Summary and recommendation
Hex supports SCIM Directory Sync for automated user provisioning, but only on the Enterprise plan with custom pricing. Teams on Professional ($36/editor/month) or Team ($75/editor/month) plans have no access to SCIM functionality. Additionally, Hex's SSO implementation uses OIDC protocol only—SAML is not supported, which can complicate integration with some identity providers that rely heavily on SAML.
For growing analytics teams, this creates a significant barrier. Moving from Team ($75/editor/month) to Enterprise just for SCIM means jumping to custom pricing that typically represents a substantial increase. Without SCIM, IT teams must manually manage user accounts in Hex—onboarding new data analysts, updating permissions as roles change, and ensuring prompt deprovisioning when employees leave. In analytics environments where access to sensitive data is critical, manual processes create security gaps and compliance risks.
The strategic alternative
Hex gates SCIM behind Enterprise. That can unlock provisioning, but it still does not complete the offboarding, access review, or license workflow across the rest of your stack. Stitchflow builds and maintains the IT workflows your team still runs manually, across every app, including the ones without APIs.
Quick SCIM facts
| SCIM available? | Yes |
| SCIM tier required | Enterprise |
| SSO required first? | No |
| SSO available? | Yes |
| SSO protocol | SAML 2.0 |
| Documentation | Not available |
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 Hex accounts manually. Here's what that costs:
The Hex pricing problem
Hex gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Plan Structure (Billed Annually)
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Community | $0 | ||
| Professional | $36/editor/month | ||
| Team | $75/editor/month | ||
| Enterprise | Custom pricing |
Note: SSO uses OIDC protocol only - SAML is not supported. Admin workspace role required to configure SSO integration.
What this means in practice
Moving from Team tier to Enterprise for SCIM access:
| Team Size | Annual Team Cost | Enterprise Upgrade Impact |
|---|---|---|
| 10 editors | $9,000/year | Custom pricing required |
| 25 editors | $22,500/year | Custom pricing required |
| 50 editors | $45,000/year | Custom pricing required |
Calculation: $75 × editors × 12 months (Team tier baseline)
Enterprise pricing is custom/negotiated, but industry patterns suggest 2-4x markup over published tiers for similar analytics platforms.
Additional constraints
Summary of challenges
- Hex supports SCIM but only at Enterprise tier (Custom)
- 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
Hex doesn't sell SCIM à la carte. It's bundled with Enterprise features:
Stitchflow Insight
The Enterprise plan is custom-priced and includes extensive administrative controls beyond basic provisioning. If you need enterprise-grade data governance and security features anyway, the upgrade may make sense. If you just want automated user provisioning, you're paying for a comprehensive enterprise bundle you won't fully use. We estimate ~80% of Enterprise features are irrelevant for teams that only need SCIM.
What IT admins are saying
Community sentiment on Hex's Enterprise-only SCIM requirement is consistently frustrated. Common complaints:
- Being locked out of basic identity automation without Enterprise pricing
- No SAML support - forced to use OIDC protocol only
- Having to negotiate custom Enterprise pricing just for user provisioning
- The massive gap between $75/editor Team plan and Enterprise for SCIM access
We're a mid-size team that just needs automated user provisioning, but Hex forces you into their Enterprise tier. The pricing jump is brutal.
Only OIDC support is limiting - most enterprises standardized on SAML years ago. Having to reconfigure our identity stack just for Hex is a non-starter.
The recurring theme
Hex gates essential identity management behind expensive Enterprise upgrades, creating a significant barrier for growing teams that need automated provisioning but can't justify custom enterprise pricing.
The decision
| Your Situation | Recommendation |
|---|---|
| On Professional or Team, need SCIM | Use Stitchflow: avoid the Enterprise tier jump |
| Already on Enterprise plan | Use native SCIM: you're paying for it |
| Need Enterprise features beyond SCIM | Evaluate Enterprise: SCIM comes bundled |
| Only using OIDC for SSO (no SAML needed) | Consider native if Enterprise is justified |
| Small analytics team, low user changes | Manual may work: but watch for security gaps |
The bottom line
Hex gates SCIM behind Enterprise. The upgrade may unlock provisioning, but the workflow still has to complete across the rest of your stack.
Close the Hex workflow gap
Hex gates SCIM behind Enterprise, but the bigger issue is the workflow around it. Stitchflow builds and maintains the offboarding, access review, or license workflow underneath.
Technical specifications
SCIM Version
2.0
Supported Operations
Create, Update, Deactivate, Groups
Supported Attributes
Not specifiedPlan requirement
Enterprise
Prerequisites
None
Key limitations
- SCIM and SSO only available on Enterprise plan
- SSO uses OIDC protocol only - SAML not supported
- Admin workspace role required to configure SSO
Documentation not available.
Close the workflow gap in
Hex
Hex gates SCIM behind Enterprise plan. That can unlock provisioning, but it still does not complete the offboarding, access review, or license workflow across your stack.
Start with the free gap diagnostic
