Summary and recommendation
WalkMe supports SCIM provisioning, but only on Enterprise plans starting at ~$43K-79K annually (up to $405K for larger deployments). The SCIM implementation covers basic user lifecycle management—creating, updating, and deactivating users—but lacks group provisioning capabilities. More concerning: WalkMe is migrating to a new Okta-powered SSO infrastructure with legacy SSO ending June 30, 2025, creating potential disruption for existing integrations.
For organizations deploying WalkMe as a company-wide digital adoption platform, this creates a significant operational challenge. Without automated provisioning, IT teams must manually manage user accounts across potentially thousands of employees who need access for training and guidance workflows. The Enterprise pricing barrier means many organizations either accept manual user management or pay premium costs primarily to unlock basic provisioning automation.
The strategic alternative
WalkMe 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 |
| Documentation | Official docs |
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 WalkMe accounts manually. Here's what that costs:
The WalkMe pricing problem
WalkMe gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Plan Structure
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Enterprise | Custom (~$43K-79K/year average) |
Note: WalkMe only offers Enterprise pricing with custom quotes. No lower tiers provide SCIM access. Basic user management requires manual processes or API integration.
What this means in practice
WalkMe's all-or-nothing pricing model forces organizations into expensive Enterprise contracts just for provisioning:
| Organization Size | Minimum Annual Cost | Per-User Impact |
|---|---|---|
| 500 users | ~$43K | $86/user/year |
| 1,000 users | ~$79K | $79/user/year |
| 2,000+ users | $79K-405K | $40-200/user/year |
Since WalkMe is typically deployed organization-wide as a digital adoption platform, even mid-size companies face substantial costs purely for user management automation.
Additional constraints
Summary of challenges
- WalkMe supports SCIM but only at Enterprise tier (Custom (~$43K-79K/year average, up to $405K))
- 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
WalkMe doesn't sell SCIM separately—it's only available on their Enterprise tier, which comes with a full digital adoption platform and extensive bundled features:
The SCIM implementation itself is also limited—no group provisioning support, and it's tied to WalkMe's new Okta-based SSO infrastructure (legacy SSO ends June 2025). You're essentially paying enterprise software prices for basic provisioning capabilities.
Stitchflow Insight
The reality: if you only need user provisioning automation, you're paying $43K-79K annually for a comprehensive digital adoption platform you may not fully utilize. We estimate ~80% of Enterprise features are irrelevant for organizations that simply want automated user management for their existing WalkMe deployment.
What IT admins are saying
Community sentiment on WalkMe's SCIM implementation centers on cost barriers and platform changes. Common complaints:
- SCIM requiring Enterprise tier pricing that averages $43K-79K annually
- Custom quote pricing making it impossible to budget for provisioning needs
- Forced migration from legacy SSO to new Okta-powered infrastructure by June 2025
- Limited IdP support excluding Google Workspace and OneLogin entirely
The pricing is completely opaque - you can't even get a ballpark without going through their sales process, and then they hit you with enterprise-level costs just for user automation.
Having to rebuild our entire SSO setup because they're EOLing the old system... and now we're locked into their Okta-based approach whether we want it or not.
The recurring theme
WalkMe treats SCIM as an enterprise-only luxury, forcing organizations into expensive custom contracts and platform migrations just to automate user lifecycle management for what should be basic identity operations.
The decision
| Your Situation | Recommendation |
|---|---|
| Need SCIM but not ready for $43K+ Enterprise | Use Stitchflow: start with a free gap diagnostic, then build the workflow across every app without asking your team to own the plumbing. |
| Already on Enterprise plan | Use native SCIM: you're paying premium pricing, leverage what's included |
| Using Okta with existing WalkMe deployment | Evaluate native first: strong Okta integration with Schema Discovery |
| Multi-IdP environment (Google, OneLogin, etc.) | Use Stitchflow: native SCIM only works with Okta and Azure AD |
| Small deployment, minimal user changes | Manual provisioning may work: but plan for scaling challenges |
The bottom line
WalkMe gates SCIM behind Enterprise. The upgrade may unlock provisioning, but the workflow still has to complete across the rest of your stack.
Close the WalkMe workflow gap
WalkMe 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
- Legacy SSO EOL June 30, 2025
- IDP-initiated login not supported - SP-initiated only
- New SSO infrastructure powered by Okta
- SAML accounts authenticated against IDP 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).
Enterprise required for SCIM
WalkMe 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
WalkMe
WalkMe 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


