Summary and recommendation
Totango supports SCIM 2.0 provisioning, but only on Enterprise plans with custom pricing. The free Community tier and standard paid plans don't include SCIM functionality. Additionally, Totango requires SSO configuration as a prerequisite before SCIM can be enabled, creating a two-step implementation process that adds complexity for IT teams managing multiple customer success tools.
This creates a significant cost barrier for mid-market organizations that need automated user provisioning but don't require Enterprise-level features. Without SCIM, IT teams must manually manage user lifecycle in Totango—creating accounts for new customer success managers, updating permissions when roles change, and deprovisioning users when they leave. This manual overhead becomes particularly problematic as customer success teams scale and user turnover increases.
The strategic alternative
Totango 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 | Not available |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | ✓ | ✓ | OIN app with full provisioning |
| Microsoft Entra ID | ✓ | ❌ | SSO only |
| 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 Totango accounts manually. Here's what that costs:
The Totango pricing problem
Totango gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Plan Structure
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Community | Free | ||
| Pro | Custom | ||
| Business | Custom | ||
| Enterprise | Custom |
Note: Totango requires SSO configuration as a prerequisite for SCIM setup, meaning you need both features bundled together.
What this means in practice
Without published pricing, IT teams face significant challenges:
The lack of transparent pricing means even small teams using Totango for customer success workflows must navigate enterprise sales processes just to enable basic user provisioning.
Additional constraints
Summary of challenges
- Totango 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
Totango doesn't sell SCIM à la carte. It's bundled with Enterprise plan features:
The free Community tier offers basic functionality but excludes all identity management features entirely.
Stitchflow Insight
If you need enterprise-grade customer success tools anyway, the upgrade may make sense. If you just want automated user provisioning, you're paying for a comprehensive customer success platform 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 Totango's SCIM implementation is mixed, with frustration centered on enterprise-only availability and SSO prerequisites. Common complaints:
- Enterprise tier requirement locks out smaller customer success teams
- Mandatory SSO configuration before SCIM adds deployment complexity
- Custom enterprise pricing makes budget planning difficult
- Limited IdP support (Okta only for provisioning, no Entra support)
We're a 50-person company using Totango for customer health scoring. Having to upgrade to Enterprise just for user provisioning doesn't make financial sense when we're already paying for identity management.
The SSO-first requirement is annoying. We just want automated user lifecycle, not necessarily single sign-on right now.
The recurring theme
Totango forces teams into expensive enterprise contracts and complex SSO deployments just to get basic user provisioning, pricing out smaller customer success operations.
The decision
| Your Situation | Recommendation |
|---|---|
| On Pro/Business tier, need SCIM | Use Stitchflow: avoid the Enterprise tier jump and custom pricing |
| Enterprise tier but SCIM setup is complex | Use Stitchflow: skip the SSO prerequisite and technical overhead |
| Using Entra ID (no native SCIM support) | Use Stitchflow: Microsoft users have no native option |
| Already on Enterprise with SSO configured | Use native SCIM: you're paying for it and have prerequisites met |
| Small customer success team, low turnover | Manual may work initially: but plan for growth and compliance needs |
The bottom line
Totango restricts SCIM to Enterprise tier with custom pricing, plus requires SSO as a prerequisite - creating barriers even for paying customers. For teams on lower tiers or using Entra ID, Stitchflow delivers the same provisioning outcomes without tier upgrades or SSO dependencies.
Make Totango workflows AI-native
Totango 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 tier required for SCIM
- SSO configuration required before SCIM
- Free Community tier does not include SCIM
Documentation not available.
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).
Docs
Full SCIM provisioning support
Totango gates SCIM behind Enterprise. Stitchflow automates complete workflows without that SCIM Tax upgrade.
Configuration for Entra ID
Integration type
Microsoft Entra Gallery app
Prerequisite
SSO must be configured before enabling SCIM.
Where to enable
SSO via SAML only
Use Stitchflow for automated provisioning.
Unlock SCIM for
Totango
Totango gates SCIM behind Enterprise plan. We automate complete offboarding and access reviews across your stack without that SCIM Tax upgrade.
See how it works
