Stitchflow
Moz logo

Moz SCIM guide

Connector Only

How to automate Moz user provisioning, and what it actually costs

Summary and recommendation

Moz Pro, the SEO platform used by marketing teams and agencies, does not offer native SCIM provisioning. While Moz supports SSO through SAML 2.0 and OpenID Connect via OneLogin, Ping Identity, and other third-party connectors, user provisioning is only available through OneLogin's specific connector. This creates a significant limitation: if your organization uses Okta, Entra ID, or Google Workspace, you're forced into manual user management despite paying up to $599/month for Premium plans.

This OneLogin-only provisioning creates a real operational burden for IT teams. Most enterprises standardize on a single identity provider, and being locked into OneLogin just for Moz provisioning means either switching IdPs entirely (costly and disruptive) or accepting the security and compliance risks of manual user lifecycle management. When SEO teams need rapid access to campaign data and keyword tracking, manual provisioning delays can directly impact marketing operations.

The strategic alternative

Moz has no native SCIM. Automate offboarding, user access reviews, and license workflows across every app, including the ones without APIs. We maintain the integration layer underneath. You focus on judgment, not plumbing.

Quick SCIM facts

SCIM available?No
SCIM tier requiredN/A
SSO required first?No
SSO available?Yes
SSO protocolSAML 2.0, OpenID Connect
DocumentationNot available

Supported identity providers

IdPSSOSCIMNotes
OktaVia third-partyNo Moz Pro app found in OIN catalog with SCIM. SSO via custom SAML setup only.
Microsoft Entra IDVia third-partyNo native Entra ID integration documented. Use OneLogin for provisioning or manual user management.
Google WorkspaceVia third-partyNo native support
OneLoginVia third-partyNo native support

The cost of not automating

Without SCIM (or an alternative like Stitchflow), your IT team manages Moz accounts manually. Here's what that costs:

Source: Stitchflow aggregate data across apps with 2+ instances, normalized to 500 employees
Orphaned accounts (ex-employees with access)7
Unused licenses12
IT hours spent on manual management/year101 hours
Unused license cost/year$3,925
IT labor cost/year$6,088
Cost of compliance misses/year$1,741
Total annual financial impact$11,754

The Moz pricing problem

Moz gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.

Tier comparison

PlanPriceSSOSCIM
Starter$49/month
Standard$99/month
Medium$179/month
Large$299/month
Premium$599/month

Provisioning options

PlanPriceSCIMProvisioning Method
Starter$49/month❌ Not availableManual only
Standard$99/month❌ Not availableManual only
Medium$179/month❌ Not availableManual only
Large$299/month❌ Not availableManual only
Premium$599/month❌ Not availableOneLogin connector only

What this means in practice

Limited IdP compatibility: If you're using Okta, Entra ID, or Google Workspace, you'll need to manage Moz users manually. Only OneLogin customers get automated provisioning through their proprietary connector.

No standardized API: Moz doesn't expose SCIM endpoints, meaning custom integrations aren't possible. You're locked into either manual user management or OneLogin's specific implementation.

SSO without provisioning: While Moz supports SAML SSO through multiple providers (OneLogin, Ping Identity, AuthDigital), this only handles authentication—not user lifecycle management.

Additional constraints

Vendor dependency
Provisioning requires OneLogin as your primary IdP, regardless of your current identity infrastructure
Manual offboarding risk
Without automated deprovisioning, former employees may retain access to SEO data and competitor intelligence
Scaling limitations
Adding new team members to SEO campaigns requires manual account creation and role assignment
No JIT provisioning
Users must be pre-created in Moz before they can authenticate via SSO

Summary of challenges

  • Moz does not provide native SCIM at any price tier
  • Organizations must rely on third-party tools or manual provisioning
  • Our research shows teams manually provisioning this app spend significant hidden costs annually

What Moz actually offers for identity

OneLogin Connector (Third-party provisioning)

Moz provides user provisioning exclusively through OneLogin's marketplace connector:

FeatureDetails
ProtocolOneLogin's proprietary API
Supported operationsCreate, update, delete users
Entitlement managementYes (role assignments)
Real-time syncYes
IdP requirementOneLogin only

Major limitation: This provisioning option only works if your organization uses OneLogin as its primary identity provider. Teams using Okta, Entra ID, or Google Workspace are locked out entirely.

SAML SSO (Multiple providers)

Moz supports federated SSO through several identity providers:

SettingDetails
ProtocolSAML 2.0, OpenID Connect
Supported IdPsOneLogin, Ping Identity, AuthDigital
ConfigurationProvider-specific setup required
JIT provisioning❌ No
User requirementManual account creation before SSO login

Okta Integration Status

The Okta Integration Network shows no native Moz Pro application:

FeatureSupported?
SAML SSO❌ No native app
OIDC SSO❌ No native app
SCIM provisioning❌ No
Custom SAML✓ Manual setup only

Translation: Okta customers must configure SAML manually and handle all user provisioning through manual processes or CSV imports.

Why this approach fails at scale

The OneLogin-only provisioning creates a significant vendor lock-in problem. If your team uses any other IdP, you're stuck with manual user management across all Moz pricing tiers—from the $49/month Starter plan to the $599/month Premium plan. There's no native SCIM endpoint that works universally with modern identity providers.

What IT admins are saying

Moz's lack of native SCIM provisioning forces IT teams into vendor-specific workarounds:

  • No standard SCIM endpoint means you're locked into specific IdP connectors
  • OneLogin is the only documented provisioning path - limiting IdP flexibility
  • Manual user management required for Okta and Entra ID environments
  • SSO setup requires custom SAML configuration instead of pre-built connectors

"User provisioning (create/update/delete) and entitlement management" only works through OneLogin's connector, according to their marketplace documentation.

The recurring theme

Moz's SEO platform forces architectural decisions around your identity provider. If you're not using OneLogin, you're managing Moz users manually despite having enterprise-grade identity infrastructure.

The decision

Your SituationRecommendation
Small SEO team (<10 users)Manual management is acceptable
Using OneLogin as your IdPOneLogin's native provisioning connector handles automation
Large marketing organization (50+ users)Use Stitchflow: automation essential across team sizes
Multi-IdP environment (Okta, Entra, etc.)Use Stitchflow: OneLogin-only provisioning creates IdP lock-in
Enterprise with compliance requirementsUse Stitchflow: automation essential for audit trail

The bottom line

Moz Pro is a leading SEO platform, but provisioning automation is limited to OneLogin users only. If you're on Okta, Entra ID, or Google Workspace, you're stuck with manual user management. For teams that want provisioning automation regardless of their IdP choice, Stitchflow eliminates the OneLogin dependency.

Make Moz workflows AI-native

Moz has no native SCIM. We build complete offboarding, user access reviews, and license workflows across every app, including the ones without APIs.

Covers apps without native SCIM, including the ones without APIs
Less than a week, start to finish (~2 hours of your time)
Built with your team; extend to anything else in the company
Book a Demo

Technical specifications

SCIM Version

Not specified

Supported Operations

Not specified

Supported Attributes

No native SCIM endpoint documentedProvisioning via OneLogin integrationSSO via third-party connectors

Plan requirement

Not specified

Prerequisites

Not specified

Key limitations

  • No native SCIM endpoint documented
  • Provisioning via OneLogin integration
  • SSO via third-party connectors

Documentation not available.

Configuration for Okta

Integration type

Okta Integration Network (OIN) app

Where to enable

Okta Admin Console → Applications → Moz → Sign On

No Moz Pro app found in OIN catalog with SCIM. SSO via custom SAML setup only.

Use Stitchflow for automated provisioning.

Unlock SCIM for
Moz

Moz has no native SCIM. We still automate end-to-end workflows across every app, including the ones without APIs.

See how it works
Admin Console
Directory
Applications
Moz logo
Moz
via Stitchflow

Last updated: 2026-01-11

* Pricing and features sourced from public documentation.

Keep exploring

Related apps

SEMrush logo

SEMrush

No SCIM

SEO / Marketing

ProvisioningNot Supported
Manual Cost$11,754/yr

Semrush, the SEO and marketing intelligence platform, does not offer SCIM provisioning on any plan—including their Enterprise tier with custom pricing. While Semrush supports SAML 2.0 SSO for authentication (which requires contacting product support to enable), this only handles login, not user lifecycle management. IT teams must manually create, update, and deprovision user accounts across what can be hundreds of marketing team members, contractors, and agencies accessing competitive intelligence and campaign data. This creates a significant operational burden for organizations managing large marketing teams or multiple agencies. Without automated provisioning, IT admins face ongoing manual work for every team member change, plus the security risk of orphaned accounts when people leave projects or change roles. For a platform that often contains sensitive competitive intelligence and campaign performance data, manual user management creates both compliance gaps and unnecessary administrative overhead.

View full guide
seoClarity logo

seoClarity

No SCIM

SEO / Marketing

ProvisioningNot Supported
Manual Cost$11,754/yr

seoClarity, the enterprise SEO platform, does not support SCIM provisioning on any documented plan. While seoClarity offers SAML SSO integration with identity providers like Okta and Azure AD, their SSO/SCIM capabilities are not publicly documented—you must contact their sales team for enterprise security features. This creates uncertainty for IT teams evaluating provisioning options, especially when seoClarity's pricing starts at $4,500+/month for full Enterprise access with unlimited users included. The lack of documented SCIM support means IT teams face manual user lifecycle management for a platform that often has broad access across SEO, marketing, and content teams. With seoClarity's enterprise positioning and premium pricing, the absence of automated provisioning creates an operational gap that doesn't align with the platform's sophisticated feature set and cost structure.

View full guide
6sense logo

6sense

No SCIM

B2B Revenue Intelligence / ABM

ProvisioningNot Supported
Manual Cost$11,754/yr

6sense, the B2B revenue intelligence platform, has paused SCIM provisioning for new customers until Q4 2026. While existing customers with SCIM enabled can continue using it, new implementations are limited to JIT (Just-In-Time) provisioning through SAML SSO. This creates a significant gap for IT teams managing revenue intelligence access, as JIT only creates users on first login and provides minimal attribute mapping (email, first name, last name only). For an enterprise platform with typical pricing of $55,000-$130,000 annually, the absence of automated user lifecycle management is a substantial limitation. The lack of SCIM until Q4 2026 forces IT teams into manual provisioning workflows for a platform handling sensitive revenue data. While SAML SSO handles authentication, it doesn't address user lifecycle events like role changes, department transfers, or offboarding. This creates compliance risks in revenue teams where access to prospect data and sales intelligence must be tightly controlled. The nearly two-year wait for SCIM restoration means organizations implementing 6sense today face manual user management for the foreseeable future.

View full guide