Summary and recommendation
Bigtincan's SCIM provisioning story is confusing and inconsistent. While Okta's integration directory shows SCIM provisioning support with Group Linking and Schema Discovery, Bigtincan provides no public documentation confirming SCIM capabilities, pricing requirements, or setup instructions. This creates a problematic situation for IT teams: you can't evaluate or plan for automated user provisioning without contacting sales first. Meanwhile, Bigtincan only offers SAML 2.0 SSO authentication, which doesn't handle user lifecycle management.
For sales enablement platforms like Bigtincan where teams frequently change territories, roles, and access permissions, this documentation gap creates real operational challenges. Sales teams have high turnover, and manually managing user accounts while ensuring proper content access by role becomes a significant burden. The lack of transparent SCIM information means IT teams can't assess whether Bigtincan will integrate with their existing identity management workflows before committing to enterprise pricing.
The strategic alternative
Bigtincan has no native SCIM. That leaves a workflow gap in offboarding, access reviews, and license cleanup unless your team handles the app another way. 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? | 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 | ✓ | ❌ | OIN integration supports provisioning with Group Linking and Schema Discovery. |
| Microsoft Entra ID | ✓ | ❌ | SAML 2.0 SSO supported. No documented SCIM provisioning with Entra ID. |
| 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 Bigtincan accounts manually. Here's what that costs:
The Bigtincan pricing problem
Bigtincan gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Standard | Contact vendor | ||
| Enterprise | Contact vendor |
Pricing structure
| Plan | Pricing | SCIM | SSO |
|---|---|---|---|
| Standard | Contact vendor | Unknown | ✓ SAML 2.0 |
| Enterprise | Contact vendor | Unknown | ✓ SAML 2.0 |
Key issue: Bigtincan requires contacting sales for all pricing and enterprise feature details, including SCIM availability.
What this means in practice
Documentation gaps create friction
Inconsistent IdP support
Additional constraints
Summary of challenges
- Bigtincan 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 Bigtincan actually offers for identity
SAML SSO (Availability Unknown)
Bigtincan supports SAML 2.0 integration, but documentation is extremely limited:
| Setting | Details |
|---|---|
| Protocol | SAML 2.0 |
| Supported IdPs | Generic SAML providers, Salesforce Identity |
| Configuration | Contact vendor for setup |
| User requirement | Unknown - no public documentation |
Critical gap: Bigtincan provides no public documentation on their SSO implementation, setup process, or user provisioning requirements.
Okta Integration (via OIN)
The official Okta Integration Network listing shows surprisingly robust provisioning support:
| Feature | Supported? |
|---|---|
| SAML SSO | ✓ Yes |
| OIDC SSO | ❌ No |
| SCIM provisioning | ✓ Yes |
| Create users | ✓ Yes |
| Update users | ✓ Yes |
| Deactivate users | ✓ Yes |
| Group push | ✓ Yes |
Microsoft Entra Integration
Entra ID support is limited to basic SSO:
| Feature | Supported? |
|---|---|
| SAML SSO | ✓ Yes |
| OIDC SSO | ❌ No |
| SCIM provisioning | ❌ No |
| Create users | ❌ No |
The documentation problem: While Okta's OIN suggests full SCIM capabilities exist, Bigtincan's own website provides zero public documentation about identity management features, pricing requirements, or setup processes. This forces IT teams to engage sales just to understand basic authentication options.
For sales enablement platforms where user turnover is high and territory-based access is critical, this lack of transparency creates unnecessary friction in the evaluation process.
What IT admins are saying
Bigtincan's lack of transparent identity management documentation creates uncertainty for IT teams:
- No public SCIM documentation despite Okta integration claiming SCIM support
- Enterprise features require contacting sales rather than self-service setup
- Mixed messaging between vendor documentation and third-party integrations
- Limited SSO options beyond SAML 2.0 and Salesforce Identity
User accounts must exist in Bigtincan to use single sign-on... Contact your Bigtincan administrator for account creation.
We had to go through sales just to understand what identity management features were actually available on our plan.
The recurring theme
Sales enablement platforms like Bigtincan often hide their provisioning capabilities behind enterprise sales processes, forcing IT teams into lengthy vendor conversations just to understand basic authentication options.
The decision
| Your Situation | Recommendation |
|---|---|
| Small sales team (<20 users) with low turnover | Manual management is acceptable |
| Enterprise with documented identity requirements | Use Stitchflow: Bigtincan's lack of public SCIM docs creates compliance gaps |
| High sales team turnover or seasonal reps | Use Stitchflow: automation essential for rapid onboarding/offboarding |
| Multi-territory sales org with role-based content access | Use Stitchflow: automated group assignments prevent access errors |
| Using Okta with existing SCIM workflows | Use Stitchflow: Okta's OIN integration may work but lacks vendor documentation support |
The bottom line
Bigtincan has no native SCIM. That means one more workflow gap in offboarding, access reviews, and license cleanup unless your team handles it another way.
Close the Bigtincan workflow gap
Bigtincan is one gap in a broader workflow. Stitchflow builds and maintains the offboarding, access review, or license workflow across every app in your environment.
Technical specifications
SCIM Version
Not specifiedSupported Operations
Not specifiedSupported Attributes
Plan requirement
Not specifiedPrerequisites
Not specifiedKey limitations
- No public SCIM documentation found
- No public SSO documentation found
- Contact vendor for enterprise features
Documentation not available.
Configuration for Okta
Integration type
Okta Integration Network (OIN) app
Where to enable
Docs
OIN integration supports provisioning with Group Linking and Schema Discovery.
Use Stitchflow for automated provisioning.
Close the workflow gap in
Bigtincan
Bigtincan has no native SCIM. That leaves one more workflow gap in offboarding, access reviews, and license cleanup unless your team handles it another way.
Start with the free gap diagnostic
