Summary and recommendation
Vitally, the customer success platform, does not offer SCIM provisioning on any plan, including their Enterprise tier. While Vitally supports SAML SSO integration with Okta and Microsoft Entra ID for authentication, user accounts must still be created and managed manually within the platform. This creates a significant operational gap for IT teams managing customer success teams at scale, where user provisioning, deprovisioning, and attribute updates must be handled through manual processes or CSV imports.
The lack of automated provisioning becomes particularly problematic for customer success organizations that need to quickly onboard new team members, manage role changes, or ensure immediate access removal when employees leave. Without SCIM, IT teams face compliance risks from delayed deprovisioning and operational overhead from manual account management across what is often a critical revenue-impacting platform.
The strategic alternative
Vitally has no native SCIM. Automate offboarding, user access reviews, and license workflows across every app, including the ones without APIs. We maintain the integration layer underneath. You focus on judgment, not plumbing.
Quick SCIM facts
| SCIM available? | No |
| SCIM tier required | N/A |
| SSO required first? | No |
| SSO available? | Yes |
| SSO protocol | SAML 2.0 |
| Documentation | Not available |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | ✓ | ❌ | SSO only via SAML |
| Microsoft Entra ID | ✓ | ❌ | SSO via SAML |
| Google Workspace | Via third-party | ❌ | No native support |
| OneLogin | Via third-party | ❌ | No native support |
The cost of not automating
Without SCIM (or an alternative like Stitchflow), your IT team manages Vitally accounts manually. Here's what that costs:
The Vitally pricing problem
Vitally gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Pro | Not disclosed | ||
| Business | Not disclosed | ||
| Enterprise | Custom quote |
Pricing structure
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Pro | Not disclosed | ||
| Business | Not disclosed | ||
| Enterprise | Custom quote |
What this means in practice
Without SCIM support, IT teams face significant operational overhead:
For a customer success platform handling sensitive customer data, these manual processes create both security risks and compliance challenges.
Additional constraints
Summary of challenges
- Vitally does not provide native SCIM at any price tier
- Organizations must rely on third-party tools or manual provisioning
- Our research shows teams manually provisioning this app spend significant hidden costs annually
What Vitally actually offers for identity
SAML SSO Only
Vitally supports SAML 2.0 integration but stops there:
| Setting | Details |
|---|---|
| Protocol | SAML 2.0 |
| Supported IdPs | Okta, Entra ID, other SAML providers |
| Provisioning | None - manual user management only |
| User requirement | Accounts must be created manually in Vitally |
The gap: While Vitally handles authentication through SAML SSO, there's no automated user lifecycle management. Every user addition, role change, and deactivation requires manual work in the Vitally admin console.
Okta Integration (SSO only)
The official Okta Integration Network listing for Vitally confirms the limitations:
| Feature | Supported? |
|---|---|
| SAML SSO | ✓ Yes |
| Create users | ❌ No |
| Update users | ❌ No |
| Deactivate users | ❌ No |
| Group sync | ❌ No |
| Role assignment | ❌ No |
The reality for customer success teams
Customer success platforms see frequent user changes as team members join accounts, switch territories, or leave the company. Without automated provisioning:
Vitally's custom enterprise pricing makes these manual processes even more expensive to maintain at scale.
What IT admins are saying
Vitally's lack of automated provisioning forces IT teams into manual user management workflows:
- Manual user creation required for every new team member
- No automated deprovisioning when employees leave the company
- SSO authentication available, but provisioning must be handled separately
- IT teams must maintain user lists in both their IdP and Vitally
Even though we have SSO set up, I still have to manually create every user account in Vitally before they can access the platform. It defeats the purpose of having centralized identity management.
The biggest pain point is offboarding. When someone leaves, I have to remember to remove them from Vitally manually since there's no automated deprovisioning. It's a security risk we shouldn't have to manage.
The recurring theme
Vitally supports SSO for authentication but leaves IT teams manually managing the entire user lifecycle. This creates operational overhead and potential security gaps when user access isn't properly synchronized between systems.
The decision
| Your Situation | Recommendation |
|---|---|
| Small customer success team (<10 users) | Manual management is workable |
| Growing SaaS with stable CS team | Manual management with SSO for security |
| Scaling customer success org (25+ users) | Use Stitchflow: automation essential for growth |
| Enterprise with compliance requirements | Use Stitchflow: automation essential for audit trail |
| Multi-team customer operations | Use Stitchflow: automation strongly recommended |
The bottom line
Vitally is a robust customer success platform, but it completely lacks automated user provisioning capabilities. You're stuck with manual user management regardless of your plan or budget. For customer success teams that need provisioning automation without the operational overhead, Stitchflow delivers SCIM-level functionality that Vitally simply doesn't offer.
Make Vitally workflows AI-native
Vitally has no native SCIM. We build complete offboarding, user access reviews, and license workflows across every app, including the ones without APIs.
Technical specifications
SCIM Version
Not specifiedSupported Operations
Not specifiedSupported Attributes
Plan requirement
Not specifiedPrerequisites
Not specifiedKey limitations
- No SCIM support available
- Manual user provisioning required
- SSO available for authentication
Documentation not available.
Configuration for Okta
Integration type
Okta Integration Network (OIN) app
Where to enable
Docs
SSO only via SAML
Use Stitchflow for automated provisioning.
Unlock SCIM for
Vitally
Vitally has no native SCIM. We still automate end-to-end workflows across every app, including the ones without APIs.
See how it works


