Stitchflow
Sanity logo

Sanity SCIM guide

Connector Only

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

Summary and recommendation

Sanity, the popular headless CMS platform, does not support SCIM provisioning on any plan. Instead, Sanity relies entirely on SAML-based role mapping for user management, where users are automatically provisioned with assigned roles on their first SSO login. While this Just-in-Time (JIT) approach works for initial user creation, it creates significant gaps in user lifecycle management - you cannot centrally deprovision users, update role assignments, or sync organizational changes from your identity provider back to Sanity projects.

This SAML-only approach leaves IT administrators with a critical blind spot: once users are provisioned through SSO, there's no automated way to remove access when employees leave or change roles. For organizations managing multiple Sanity projects with different access requirements, this means manual user management becomes unavoidable, creating both security risks and administrative overhead that scales poorly with team growth.

The strategic alternative

Sanity 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
DocumentationNot available

Supported identity providers

IdPSSOSCIMNotes
OktaVia third-partySanity does NOT support SCIM provisioning. Uses SAML-based role mapping instead. Users are auto-provisioned with roles on first SSO login via JIT.
Microsoft Entra IDVia third-partySanity does NOT support SCIM provisioning with Azure/Entra. Uses SAML-based role mapping. JIT provisioning creates users on first login.
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 Sanity 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 Sanity pricing problem

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

Tier comparison

PlanPriceSSOSCIM
Free$0
Growth$15/user/month
Enterprise$5,000-10,000+/month starting

Pricing structure

PlanPriceSSOSCIM
Free$0
Growth$15/user/month
Enterprise$5,000-10,000+/month starting

What this means in practice

Without SCIM, IT admins lose control over the user lifecycle in Sanity:

No proactive provisioning: Users must visit Sanity and trigger SSO login before they appear in the system. You can't pre-provision accounts or set up access before users need it.

No centralized deprovisioning: When someone leaves or changes roles, you can disable their IdP access, but their Sanity account persists with whatever permissions they had. Manual cleanup is required.

Role mapping complexity: User permissions are determined by SAML attribute mapping rules configured in Sanity, not managed through your IdP's group assignments in real-time.

Additional constraints

JIT dependency
All user creation relies on the user successfully completing SSO login - no bulk imports or API-based provisioning
Role mapping limitations
Custom role mapping rules are only available on Enterprise plans, forcing smaller teams into manual user management
No offboarding automation
Departing users require manual account removal from Sanity's admin panel since SCIM suspend/delete operations don't exist
Project-level permissions
Sanity's project-based permission model can't be fully automated through IdP group memberships - requires manual project assignment

Summary of challenges

  • Sanity 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 Sanity actually offers for identity

SAML SSO with Role Mapping (Enterprise or Growth + Add-on)

Sanity provides SAML 2.0 integration with automatic role assignment:

SettingDetails
ProtocolSAML 2.0
Supported IdPsOkta, Azure AD, Google Workspace, PingIdentity
User provisioningJust-in-time (JIT) on first SSO login
Role assignmentMaps IdP groups to Sanity project roles
ConfigurationCustom mapping rules (Enterprise only)

How it works: Users are automatically created in Sanity when they first authenticate via SSO, with roles assigned based on their IdP group memberships.

What's missing: True SCIM provisioning

SCIM FeatureSanity Support
Create users❌ JIT only (requires login)
Update user attributes❌ No
Deactivate users❌ No
Sync group memberships❌ Role mapping only
Bulk operations❌ No
Real-time sync❌ No

The gap: While SAML role mapping handles basic access control, you can't proactively provision users, update their details, or automatically deactivate accounts when they leave. Users must log in at least once for their accounts to be created, and there's no way to bulk-manage user lifecycles or sync attribute changes.

What IT admins are saying

Sanity's lack of SCIM provisioning forces IT teams into manual user management workflows:

  • No automated user provisioning or deprovisioning - all account management is manual
  • Must rely on JIT provisioning through SAML, creating security gaps during offboarding
  • Role mapping requires Enterprise tier, leaving smaller teams without granular access control
  • Users can't be pre-provisioned - they must attempt login before accounts are created

Users auto-provisioned with roles on SSO login

Sanity documentation

SAML SSO on Enterprise/Growth+addon. Role mapping from IdP groups.

Sanity SSO documentation

The recurring theme

Without SCIM, IT admins lose the ability to proactively manage user lifecycles. Employees retain access until they actually try to log in and fail, and new hires can't be set up in advance of their start date.

The decision

Your SituationRecommendation
Small development team (<10 users)Manual management with SAML SSO is workable
Content teams with frequent contractor changesUse Stitchflow: JIT provisioning creates audit gaps
Enterprise with multiple Sanity projectsUse Stitchflow: role mapping across projects gets complex
Organizations requiring deprovisioning automationUse Stitchflow: SAML role mapping can't remove access
Teams needing granular role managementUse Stitchflow: native role mapping is limited to basic rules

The bottom line

Sanity's SAML-based role mapping creates users on first login, but it's a one-way street—there's no automated deprovisioning or sophisticated role management. For teams that need true provisioning automation with proper lifecycle management, Stitchflow eliminates the gaps in Sanity's JIT approach.

Make Sanity workflows AI-native

Sanity 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 SCIM provisioningUses SAML role mapping insteadCustom mapping rules on Enterprise only

Plan requirement

Not specified

Prerequisites

Not specified

Key limitations

  • No SCIM provisioning
  • Uses SAML role mapping instead
  • Custom mapping rules on Enterprise only

Documentation not available.

Configuration for Entra ID

Integration type

Microsoft Entra Gallery app

Where to enable

Entra admin center → Enterprise applications → Sanity → Single sign-on

Sanity does NOT support SCIM provisioning with Azure/Entra. Uses SAML-based role mapping. JIT provisioning creates users on first login.

Use Stitchflow for automated provisioning.

Unlock SCIM for
Sanity

Sanity 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
Sanity logo
Sanity
via Stitchflow

Last updated: 2026-01-11

* Pricing and features sourced from public documentation.

Keep exploring

Related apps

Contentful logo

Contentful

SCIM Tax

Headless CMS / Content Platform

SCIM StatusIncluded
Manual Cost$11,754/yr

Contentful supports SCIM 2.0 for automated user provisioning, but only on Premium or Enterprise plans with High Availability/Scale add-ons. This means you're looking at $60,000-$140,000+ annually just to unlock SCIM functionality. The implementation also has a critical operational risk: SCIM authorization is tied to a specific admin user account, so if that admin leaves the organization, your IdP loses provisioning access entirely. For content teams managing multiple spaces with different access requirements, manual user provisioning creates significant delays. New developers and content editors can't access the spaces they need for days, while IT teams struggle to maintain proper team assignments across complex content workflows. SSO with JIT provisioning helps with authentication but doesn't solve the core problem of getting users into the right teams and spaces from day one.

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
ActiveCampaign logo

ActiveCampaign

No SCIM

Marketing Automation / Email

ProvisioningNot Supported
Manual Cost$11,754/yr

ActiveCampaign, the marketing automation platform, does not offer native SCIM provisioning on any plan. While the Enterprise plan ($145+/month) includes SAML 2.0 SSO with just-in-time (JIT) provisioning, this only creates user accounts on first login—there's no automated deprovisioning when employees leave or change roles. New SSO users are automatically added to a generic "SSO Users" group with configurable permissions, but IT teams have no way to programmatically manage user lifecycles or enforce granular access controls based on department or role changes. This creates a significant gap for marketing teams that need to manage access to customer data and campaign tools. When employees leave the company or change departments, their ActiveCampaign access must be manually revoked, creating compliance risks and potential data exposure. The lack of automated deprovisioning means former employees could theoretically retain access to sensitive marketing data and customer information until someone manually removes them from the platform.

View full guide