Summary and recommendation
Figma supports SCIM provisioning, but only starting with the Organization plan at $55/user/month—a 244% increase from Professional ($16/user/month). Even then, Organization only provides basic SCIM functionality. Full seat management via SCIM (automatically assigning Editor vs. Admin permissions) requires Enterprise at $90/user/month. This means teams upgrading from Professional face a $74/user/month jump to get complete provisioning automation.
The March 2025 billing model changes add another complication: existing SCIM configurations may require migration, creating unexpected technical debt for IT teams who thought their provisioning was settled. For a 100-person Professional team, accessing full SCIM seat management means paying an extra $88,800/year—often just to automate what could be simple user lifecycle management.
The strategic alternative
Figma gates SCIM behind Organization or Enterprise. Skip the Organization or 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 Figma accounts manually. Here's what that costs:
The Figma pricing problem
Figma gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Plan Structure (Full Seats, Billed Annually)
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Professional | $16/user/mo | ||
| Organization | $55/user/mo | Basic | |
| Enterprise | $90/user/mo | Full |
Key distinction: Organization provides basic SCIM (create/update/deactivate users) but all provisioned users receive View-only seats by default. Upgrading to Editor/Admin requires manual intervention. Enterprise enables automatic seat type assignment via SCIM attributes.
What this means in practice
Using current list prices for SCIM access:
| Team Size | Upgrade to Organization | Upgrade to Enterprise |
|---|---|---|
| 50 users | +$23,400/year | +$44,400/year |
| 100 users | +$46,800/year | +$88,800/year |
| 200 users | +$93,600/year | +$177,600/year |
Calculation: (New tier price - $16) × users × 12 months
For teams that need true automated seat management (not just user lifecycle), Enterprise is effectively required, making the real SCIM tax $74/user/month.
Additional constraints
Summary of challenges
- Figma supports SCIM but only at Enterprise tier ($90/user/mo (annual only))
- 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
Figma doesn't sell SCIM à la carte. It's bundled with Organization/Enterprise features:
The catch: Figma's March 2025 billing model changes are forcing existing SCIM users to potentially migrate their setup, adding unexpected complexity to what should be straightforward provisioning.
Stitchflow Insight
If you need advanced design collaboration features anyway, the Organization upgrade may make sense. If you just want automated user provisioning, you're paying for design-specific features your IT team won't use. We estimate ~65% of Organization/Enterprise features are irrelevant for teams that only need SCIM provisioning.
What IT admins are saying
Community sentiment on Figma's SCIM implementation is mixed, with growing frustration over the 2025 billing changes. Common complaints:
- Confusion over Organization vs Enterprise plan differences for SCIM features
- Concern about March 2025 billing model changes disrupting existing SCIM setups
- Full seat management requiring Enterprise tier at $90/user/month
- Uncertainty about migration requirements for current SCIM users
The billing model changes in 2025 are going to be a nightmare for our SCIM setup - nobody knows exactly what we'll need to migrate.
Why does full SCIM seat management require Enterprise when basic provisioning works on Organization? The feature differentiation makes no sense.
The recurring theme
Figma's SCIM works well technically, but the upcoming billing changes and confusing plan tiers are creating uncertainty for IT teams who need reliable, long-term provisioning solutions.
The decision
| Your Situation | Recommendation |
|---|---|
| On Professional, need SCIM | Use Stitchflow: avoid the $39/user/month Organization upgrade |
| On Organization, need full seat management | Use Stitchflow: skip the $35/user/month Enterprise jump |
| Already on Enterprise with SCIM | Use native SCIM: you're paying for it, but prepare for March 2025 migration |
| Worried about March 2025 billing changes | Use Stitchflow: skip the migration complexity entirely |
| Small team, minimal user changes | Manual may work: but watch for access sprawl as design teams grow |
The bottom line
Figma gates SCIM behind Organization or Enterprise. Stitchflow automates complete workflows without that SCIM Tax upgrade.
Make Figma workflows AI-native
Figma gates SCIM behind Organization or 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
- Only Organization Admins can set up SAML SSO
- Enterprise plan required for full seat management via SCIM
- March 2025 billing changes may require SCIM migration steps
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).
Enterprise required for SCIM
Figma gates SCIM behind Organization or 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).
Enterprise required for SCIM
Figma gates SCIM behind Organization or Enterprise. Stitchflow automates complete workflows without that SCIM Tax upgrade.
Unlock SCIM for
Figma
Figma gates SCIM behind Organization or Enterprise plan. We automate complete offboarding and access reviews across your stack without that SCIM Tax upgrade, avoiding a 244% markup.
See how it works
