Summary and recommendation
Coda supports native SCIM 2.0 provisioning, but only on Enterprise plans with custom pricing. This creates a significant barrier since SCIM also requires SAML SSO to be configured first, and Coda only allows one active SCIM token at a time—regenerating a token immediately invalidates the previous one, creating operational complexity for IT teams managing multiple environments or backup configurations.
The Enterprise requirement is particularly problematic for growing teams using Coda's unique "Doc Maker" billing model. While non-makers can collaborate for free, the jump from Team ($30/doc maker/month) to Enterprise custom pricing often represents a substantial cost increase just to unlock automated provisioning. This forces IT teams to choose between manual user management or significant budget increases for features they may not need beyond SCIM.
Without automated provisioning, IT teams face manual onboarding delays and security risks when employees leave—deactivated Doc Makers' documents become read-only, potentially disrupting business-critical workflows until proper handoffs occur.
The strategic alternative
Coda 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 Coda accounts manually. Here's what that costs:
The Coda pricing problem
Coda gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Pro | $10/doc maker/month (annual) | ||
| Team | $30/doc maker/month (annual) | ||
| Enterprise | Custom pricing |
Plan Structure
| Plan | Price | SCIM |
|---|---|---|
| Pro | $10/doc maker/month (annual) | ❌ |
| Team | $30/doc maker/month (annual) | ❌ |
| Enterprise | Custom pricing | ✓ |
Note: Only Doc Makers incur charges under Coda's billing model. Editors can collaborate on documents without additional cost, but SCIM provisioning is only available with Enterprise custom contracts.
What this means in practice
Since Enterprise pricing is custom and undisclosed, organizations face several challenges:
The "Maker Billing" model creates additional complexity during sales discussions, as traditional per-seat pricing comparisons don't apply.
Additional constraints
Summary of challenges
- Coda supports SCIM but only at Enterprise tier (Custom pricing (includes SSO/SCIM))
- 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
Coda doesn't sell SCIM standalone. It's bundled with Enterprise features that require custom pricing:
Stitchflow Insight
The catch: you must configure SAML before SCIM, and only one SCIM token can be active at a time. If you need these enterprise controls anyway, the upgrade makes sense. If you just want automated user provisioning, you're paying for enterprise features you won't use. We estimate ~60% of Enterprise features are irrelevant for teams that only need SCIM.
What IT admins are saying
Community sentiment on Coda's SCIM implementation centers around accessibility barriers and implementation complexity. Common complaints:
- Enterprise-only SCIM forcing custom pricing negotiations for basic provisioning
- SAML prerequisite creating unnecessary setup dependencies
- Single SCIM token limitation complicating credential management
- Doc Maker deactivation causing unexpected workflow disruptions
Having to configure SAML before SCIM is backwards - we just want user provisioning, not full SSO rollout.
The one token at a time restriction is painful when you need to rotate credentials or test integrations.
The recurring theme
Coda's SCIM feels like an afterthought with artificial barriers that force teams into expensive Enterprise plans and complex setup processes just to automate basic user management.
The decision
| Your Situation | Recommendation |
|---|---|
| On Pro or Team, need SCIM | Use Stitchflow: avoid the Enterprise upgrade cost |
| Enterprise budget approved but long procurement cycle | Use Stitchflow: get SCIM running in days, not months |
| Already on Enterprise with SCIM enabled | Use native SCIM: you're paying for it |
| Need Enterprise features beyond SCIM | Evaluate Enterprise: SCIM comes bundled with advanced admin controls |
| Small team with low turnover | Manual may work: but watch for docs becoming orphaned when Makers leave |
The bottom line
Coda's Enterprise-only SCIM means teams on Pro ($10/maker/month) or Team ($30/maker/month) face custom Enterprise pricing to get provisioning automation. For organizations that need SCIM without the Enterprise commitment, Stitchflow delivers the same automation at predictable flat-rate pricing.
Make Coda workflows AI-native
Coda 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
- Enterprise only
- SAML must be configured before SCIM
- One SCIM token valid at a time - regenerating invalidates previous
- Deactivated Doc Makers' docs become read-only
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).
SCIM provisioning available via OIN. Supports create, update, deactivate, import, and reactivate users.
Coda 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).
Native SCIM provisioning tutorial available. SAML must be configured before SCIM.
Coda gates SCIM behind Enterprise. Stitchflow automates complete workflows without that SCIM Tax upgrade.
Unlock SCIM for
Coda
Coda gates SCIM behind Enterprise plan. We automate complete offboarding and access reviews across your stack without that SCIM Tax upgrade.
See how it works


