Summary and recommendation
Mode supports SCIM 2.0 for automated user provisioning, but only on Enterprise plans with custom pricing (typically $6,000-$50,000/year for 50+ seats). The bigger constraint: you must first configure SAML as the sole signin method before SCIM can be enabled, and you need to contact your Customer Success Manager to turn it on. This creates a rigid deployment sequence that many IT teams find unnecessarily complex.
For organizations on Business/Pro plans ($49/user/month), accessing SCIM means upgrading to Enterprise—often a 2-3x cost increase depending on team size and negotiated rates. Even teams ready to pay Enterprise pricing face the SAML prerequisite, which can complicate rollouts where you want to test provisioning before forcing all users through SSO.
The strategic alternative
Mode gates SCIM behind Enterprise. Skip the Enterprise plan upgrade and automate complete outcomes across your stack. We maintain the integration layer underneath. You focus on judgment, not plumbing.
Quick SCIM facts
| SCIM available? | Yes |
| SCIM tier required | Enterprise |
| SSO required first? | Yes |
| SSO available? | Yes |
| SSO protocol | SAML 2.0 |
| Documentation | Official docs |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | ✓ | ✓ | OIN app with full provisioning |
| Microsoft Entra ID | ✓ | ✓ | Gallery app with SCIM |
| Google Workspace | ✓ | JIT only | SAML SSO with just-in-time provisioning |
| OneLogin | ✓ | ✓ | Supported |
The cost of not automating
Without SCIM (or an alternative like Stitchflow), your IT team manages Mode accounts manually. Here's what that costs:
The Mode pricing problem
Mode gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Plan Structure
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Studio | Free (5 users) | ||
| Business/Pro | $49/user/mo | ||
| Enterprise | $6,000-$50,000/year |
Note: Enterprise requires 50+ seats minimum and includes both SAML SSO and SCIM 2.0 provisioning with full user lifecycle management and group sync.
What this means in practice
The pricing jump from Business/Pro to Enterprise creates a substantial cost increase:
| Current Monthly Spend | Enterprise Minimum | Annual Increase |
|---|---|---|
| 20 users at $980/mo | ~$6,000/year | +$23,240 |
| 50 users at $2,450/mo | ~$20,000/year | -$9,400 |
| 100 users at $4,900/mo | ~$35,000/year | -$23,800 |
Calculation assumes mid-range Enterprise pricing. Teams under 50 users face the steepest relative increase, while larger teams may find Enterprise pricing competitive with Business/Pro.
Additional constraints
Summary of challenges
- Mode supports SCIM but only at Enterprise tier (custom pricing)
- Google Workspace users get JIT provisioning only, not full SCIM
- Our research shows teams manually provisioning this app spend significant hidden costs annually
What the upgrade actually includes
Mode doesn't sell SCIM à la carte. It's bundled with Enterprise tier features starting at $6,000-50,000/year:
The catch: SAML must be configured first and set as the sole sign-in method before Mode will enable SCIM. You'll need to contact your Customer Success Manager to activate provisioning - it's not self-service.
Stitchflow Insight
If you need enterprise data analytics features anyway, the upgrade makes sense. If you just want automated user provisioning for your data team, you're paying for analytics infrastructure you may not fully utilize. We estimate ~60% of Enterprise features are irrelevant for teams that only need basic SCIM automation.
What IT admins are saying
Community sentiment on Mode's SCIM implementation is mixed, with frustration centered on the setup complexity and Enterprise requirement. Common complaints:
Mode's documentation is clear about the prerequisites, but the multi-step process creates deployment friction that other analytics platforms avoid.
- SAML must be configured as the sole signin method before SCIM can be enabled
- Requiring contact with Customer Success Manager to activate SCIM features
- Enterprise tier requirement pricing out smaller data teams
- Users losing all group memberships when deactivated through SCIM
The recurring theme
While Mode's SCIM functionality works well once configured, the SAML prerequisite and CSM activation requirement create unnecessary setup barriers for IT teams wanting straightforward identity automation.
The decision
| Your Situation | Recommendation |
|---|---|
| On Business/Pro, need SCIM | Use Stitchflow: avoid the Enterprise upgrade and $6K+ minimum |
| Already on Enterprise | Use native SCIM: you're paying for it and it works well |
| Can't make SAML the sole signin method | Use Stitchflow: bypass the SAML prerequisite entirely |
| Need SCIM enabled quickly | Use Stitchflow: no CSM approval or implementation delays |
| Small data team, low user churn | Manual may work: but watch for analysts losing access to reports |
The bottom line
Mode gates SCIM behind Enterprise. Stitchflow automates complete workflows without that SCIM Tax upgrade.
Make Mode workflows AI-native
Mode gates SCIM behind Enterprise. We build complete offboarding, user access reviews, and license workflows without that SCIM Tax upgrade.
Technical specifications
SCIM Version
2.0
Supported Operations
Create, Update, Deactivate, Groups
Supported Attributes
Not specifiedPlan requirement
Enterprise
Prerequisites
SSO must be configured first
Key limitations
- SAML must be set up before SCIM
- SAML must be sole signin method for SCIM
- Contact Customer Success Manager to enable SCIM
- Deactivated users lose all group memberships
Configuration for Okta
Integration type
Okta Integration Network (OIN) app with SCIM provisioning
Prerequisite
SSO must be configured before enabling SCIM.
Where to enable
Required credentials
SCIM endpoint URL and bearer token (generated in app admin console).
Configuration steps
Enable Create Users, Update User Attributes, and Deactivate Users.
Provisioning trigger
Okta provisions based on app assignments (users or groups).
OIN integration with SAML SSO and SCIM. Push users, deactivate, profile updates. Groups via Push Groups. SAML must be sole signin method.
Mode gates SCIM behind Enterprise. Stitchflow automates complete workflows without that SCIM Tax upgrade.
Configuration for Entra ID
Integration type
Microsoft Entra Gallery app with SCIM provisioning
Prerequisite
SSO must be configured before enabling SCIM.
Where to enable
Required credentials
Tenant URL (SCIM endpoint) and Secret token (bearer token from app admin console).
Configuration steps
Set Provisioning Mode = Automatic, configure SCIM connection.
Provisioning trigger
Entra provisions based on user/group assignments to the enterprise app.
Sync behavior
Entra provisioning runs on a scheduled cycle (typically every 40 minutes).
AAD SCIM supported. Requires SAML setup first as sole signin method. Contact CSM to enable SCIM. Users and groups supported.
Mode gates SCIM behind Enterprise. Stitchflow automates complete workflows without that SCIM Tax upgrade.
Unlock SCIM for
Mode
Mode gates SCIM behind Enterprise plan. We automate complete offboarding and access reviews across your stack without that SCIM Tax upgrade.
See how it works


