Summary and recommendation
Dixa supports SCIM provisioning, but only through its Okta integration on Enterprise plans. While this provides solid automation for Okta users—including group linking for queue assignments and schema discovery—it leaves non-Okta environments relying on manual provisioning or JIT (just-in-time) account creation. For customer service teams managing agent onboarding across multiple shifts and seasonal scaling, this creates a significant operational gap.
The real challenge is that support organizations often need rapid agent provisioning during peak seasons or crisis response, but may not have standardized on Okta or justified Enterprise pricing (custom tier above $169/agent/month). Without automated provisioning, IT teams end up manually creating accounts, assigning queue permissions, and configuring skill groups—exactly the kind of repetitive work that leads to errors during high-pressure situations.
The strategic alternative
Dixa 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? | Yes |
| SSO available? | Yes |
| SSO protocol | SAML 2.0, SWA |
| 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 Dixa accounts manually. Here's what that costs:
The Dixa pricing problem
Dixa gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Plan Structure (7-seat minimum, annual contract required)
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Essential | $49/agent/mo | ||
| Growth | $109/agent/mo | ||
| Ultimate | $169/agent/mo | ||
| Enterprise | Custom pricing |
Note: All lower tiers lack both SSO and SCIM. Enterprise bundles SAML SSO with full SCIM provisioning including group linking and schema discovery.
What this means in practice
Since Enterprise pricing is custom (typically 2-3x Ultimate tier), upgrade costs from Ultimate are significant:
| Team Size | Estimated Annual Increase* |
|---|---|
| 25 agents | +$50,700 - $76,050 |
| 50 agents | +$101,400 - $152,100 |
| 100 agents | +$202,800 - $304,200 |
*Assumes Enterprise at 2-3x Ultimate pricing ($338-$507/agent/mo vs $169/agent/mo)
Additional constraints
Summary of challenges
- Dixa 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
Dixa doesn't sell SCIM à la carte. It's bundled with Enterprise features:
The bigger issue: Dixa's SCIM is primarily designed for Okta. While they have a native SCIM API that works with other IdPs like Entra ID, you'll need to configure it manually using generic SCIM connectors—no pre-built integrations for non-Okta environments.
Stitchflow Insight
If you need enterprise-grade contact center controls anyway, the upgrade may make sense. If you just want automated user provisioning for your support team, you're paying for a bundle you won't fully use. We estimate ~60% of Enterprise features are irrelevant for teams that only need SCIM automation.
What IT admins are saying
Community sentiment on Dixa's SCIM limitations centers around integration restrictions and enterprise pricing barriers. Common complaints:
- SCIM provisioning primarily limited to Okta integration
- Requires enterprise-tier pricing for automated user management
- Limited IdP flexibility compared to other customer service platforms
- Manual provisioning fallbacks for non-Okta environments
We're stuck with manual agent onboarding because we use Azure AD and Dixa's SCIM is basically Okta-only. For a contact center with high turnover, this creates real operational overhead.
The enterprise pricing jump just for SCIM feels excessive when you're managing 20-30 support agents. We need the automation but not all the other enterprise features.
The recurring theme
Dixa's SCIM implementation favors Okta shops and requires expensive enterprise upgrades, leaving many IT teams managing agent provisioning manually despite having modern identity infrastructure.
The decision
| Your Situation | Recommendation |
|---|---|
| On Essential/Growth/Ultimate, need SCIM | Use Stitchflow: avoid the Enterprise upgrade and custom pricing negotiation |
| Already on Enterprise tier | Use native SCIM: you're paying custom pricing that likely includes it |
| Need Enterprise features beyond SCIM | Evaluate Enterprise: SCIM comes bundled with advanced workflows |
| Using non-Okta IdP (Entra, Google, OneLogin) | Use Stitchflow: simpler than configuring generic SCIM connector |
| Small support team, low agent turnover | Manual may work: but monitor queue assignment errors |
The bottom line
Dixa gates SCIM behind Enterprise. The upgrade may unlock provisioning, but the workflow still has to complete across the rest of your stack.
Close the Dixa workflow gap
Dixa 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
SSO must be configured first
Key limitations
- SCIM primarily via Okta integration
- SWA fallback for non-SAML/OIDC apps
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).
Full SCIM provisioning with group linking, schema discovery, and attribute writeback. Configuration guide available at support.dixa.help.
Dixa gates SCIM behind Enterprise. The upgrade may unlock provisioning, but the workflow still has to complete across the rest of your stack.
Close the workflow gap in
Dixa
Dixa 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


