Stitchflow
Spiff logo

Spiff SCIM guide

Native SCIM

How to automate Spiff user provisioning, and what it actually costs

Native SCIM requires Enterprise plan

Summary and recommendation

Spiff supports SCIM provisioning, but there's a catch: Spiff was acquired by Salesforce and now requires integration through the Salesforce ecosystem. This means SCIM provisioning is only available on Enterprise plans with custom pricing, and the provisioning itself is managed through Salesforce's platform rather than directly with Spiff.

For organizations using Spiff's Pro plan ($75/user/month) or seeking straightforward provisioning without Salesforce dependencies, this creates a significant barrier. The Enterprise tier requires custom pricing negotiations with Salesforce, and you're locked into their broader platform architecture. This means what should be a simple SCIM integration becomes tied to Salesforce's complex enterprise sales process and potentially much higher costs.

The strategic alternative

Spiff 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 requiredEnterprise
SSO required first?No
SSO available?Yes
SSO protocolSAML 2.0
DocumentationNot available

Supported identity providers

IdPSSOSCIMNotes
OktaOIN app with full provisioning
Microsoft Entra IDGallery app with SCIM
Google WorkspaceJIT onlySAML SSO with just-in-time provisioning
OneLoginSupported

The cost of not automating

Without SCIM (or an alternative like Stitchflow), your IT team manages Spiff accounts manually. Here's what that costs:

Source: Stitchflow research, normalized to 500 employees:
Orphaned accounts (ex-employees with access)5
Unused licenses12
IT hours spent on manual management/year85 hours
Unused license cost/year$3,500
IT labor cost/year$5,100
Cost of compliance misses/year$890
Total annual financial impact$9,490

The Spiff pricing problem

Spiff gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.

Tier comparison

PlanPriceSSOSCIM
Pro$75/user/mo
EnterpriseCustom

Plan Structure

PlanPriceSCIM
Pro$75/user/mo
EnterpriseCustom✓ (via Salesforce)

Note: SCIM provisioning is handled through Salesforce's identity platform since the acquisition. This requires coordination with Salesforce sales and potentially additional Salesforce licensing.

What this means in practice

The Salesforce integration creates several practical barriers:

Custom pricing opacity
Enterprise pricing requires direct sales engagement with both Spiff and potentially Salesforce teams
Salesforce dependency
Your Spiff provisioning becomes tied to Salesforce's platform reliability and architecture
Complex procurement
What started as a simple sales compensation tool now involves enterprise software negotiations

Additional constraints

Salesforce ecosystem lock-in
Provisioning architecture depends on Salesforce's identity platform, not native Spiff infrastructure.
Sales process complexity
Custom Enterprise pricing means lengthy procurement cycles instead of transparent self-service options.
Platform integration overhead
IT teams must understand and maintain Salesforce identity configurations even if Spiff is your only Salesforce product.
Unclear standalone viability
As Spiff becomes more integrated into Salesforce, independent operation may become increasingly complex.

Summary of challenges

  • Spiff 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

Spiff doesn't offer standalone SCIM. Since Salesforce acquired Spiff, identity management is bundled through Salesforce's Sales Cloud platform as an add-on:

SCIM 2.0 automated provisioning (via Salesforce platform)
SAML single sign-on through Salesforce Identity
Salesforce CRM integration and data sync
Advanced territory management
Custom compensation plan builders
Enterprise reporting and analytics
Salesforce ecosystem access and workflows
Dedicated Salesforce support channels

Stitchflow Insight

This creates a significant barrier: you're not just upgrading Spiff, you're buying into the entire Salesforce ecosystem. If your team already uses Salesforce CRM, this integration may provide value. But if you just need automated user provisioning for your sales compensation tool, you're paying for enterprise CRM capabilities you won't use. We estimate ~80% of the Salesforce Sales Cloud add-on features are irrelevant for teams that only want SCIM provisioning.

What IT admins are saying

Community sentiment on Spiff's identity management is mixed, with confusion around the Salesforce acquisition dominating discussions. Common complaints:

  • Uncertainty about whether existing Spiff licenses include identity features
  • Being forced into Salesforce's complex pricing model for what was once standalone software
  • Lack of clear documentation on provisioning options post-acquisition
  • Enterprise pricing now requiring Salesforce sales conversations instead of transparent costs

We were evaluating Spiff before the Salesforce acquisition, but now everything goes through their enterprise sales process. Can't even get a straight answer on pricing.

Reddit, r/sysadmin

Since Spiff became part of Salesforce, our renewal conversation turned into a pitch for Sales Cloud add-ons we don't need. Just want to keep our commission software working.

Spiceworks Community

The recurring theme

The Salesforce acquisition has created pricing opacity and complexity where there was once straightforward SaaS pricing, forcing IT teams into enterprise sales cycles for basic identity integration.

The decision

Your SituationRecommendation
On Pro plan, need SCIMUse Stitchflow: avoid the costly Enterprise upgrade
Want SCIM without Salesforce ecosystem lock-inUse Stitchflow: maintain independence from SF platform
Already integrated with Salesforce Sales CloudUse native SCIM: leverage existing Salesforce investment
Need Enterprise features beyond SCIMEvaluate Salesforce Enterprise: SCIM comes bundled
Small team, low employee turnoverManual may work: but watch for scaling issues

The bottom line

Since Salesforce's acquisition, Spiff's SCIM requires navigating the Salesforce ecosystem and Enterprise pricing. For teams that want provisioning automation without the Salesforce platform dependency, Stitchflow delivers SCIM-level functionality while preserving your independence.

Make Spiff workflows AI-native

Spiff gates SCIM behind Enterprise. We build complete offboarding, user access reviews, and license workflows without that SCIM Tax upgrade.

No Enterprise upgrade required
Less than a week, start to finish (~2 hours of your time)
We maintain the integration layer underneath
Book a Demo

Technical specifications

SCIM Version

2.0

Supported Operations

Create, Update, Deactivate, Groups

Supported Attributes

Not specified

Plan requirement

Enterprise

Prerequisites

None

Key limitations

  • Now part of Salesforce ecosystem - requires Salesforce for identity integration
  • Pricing tied to Salesforce Sales Cloud add-on model
  • Provisioning managed through Salesforce platform
  • Enterprise features require Salesforce contact

Documentation not available.

Unlock SCIM for
Spiff

Spiff gates SCIM behind Enterprise plan. We automate complete offboarding and access reviews across your stack without that SCIM Tax upgrade.

See how it works
Admin Console
Directory
Applications
Spiff logo
Spiff
via Stitchflow

Last updated: 2026-01-20

* Pricing and features sourced from public documentation.

Keep exploring

Related apps

Alteryx logo

Alteryx

SCIM Tax
SCIM StatusIncluded
Manual Cost$9,490/yr

Alteryx supports native SCIM 2.0 provisioning, but only on Enterprise plans with custom pricing (7+ users minimum). The feature requires SSO (SAML or OIDC) to be configured first and completely overrides manual user management. For teams on Professional ($5,000/user/year) or Business ($10,000-$20,000/user/year) plans, accessing SCIM means upgrading to Enterprise - often a significant cost increase for functionality that should be table stakes. This creates a provisioning gap for most Alteryx deployments. Without automated user lifecycle management, IT teams face manual onboarding/offboarding workflows, delayed access provisioning, and compliance risks around orphaned accounts. The high per-user costs make Alteryx particularly expensive to scale, and forcing an Enterprise upgrade just for basic provisioning automation compounds that challenge.

View full guide
Atlan logo

Atlan

SCIM Tax
SCIM StatusIncluded
Manual Cost$9,490/yr

Atlan supports native SCIM 2.0 provisioning with full user and group management capabilities. However, SCIM is only available on Enterprise tier, which requires custom pricing negotiations. Additionally, SSO must be enabled before SCIM can be configured, and Atlan's pricing tiers (Starter, Premier, Enterprise) are not publicly disclosed, making cost planning difficult for IT teams. This creates a significant barrier for organizations wanting automated provisioning without committing to enterprise-level contracts. For data teams evaluating Atlan, the lack of transparent pricing means you can't budget for provisioning capabilities upfront. The SSO prerequisite also forces organizations into a specific implementation sequence that may not align with their rollout timeline.

View full guide
Benchling logo

Benchling

SCIM Tax
SCIM StatusIncluded
Manual Cost$9,490/yr

Benchling supports SCIM provisioning, but only on Enterprise plans with custom pricing that typically starts at $1M+ annually. This creates a massive barrier: organizations on Professional plans ($20,000+/year) face a 50x+ price increase to unlock automated user provisioning. Even mid-sized life sciences teams end up paying enterprise-level licensing just to automate basic user lifecycle management. The pricing gap is so extreme that most organizations either stick with manual provisioning or delay Benchling adoption entirely. This creates a significant operational burden for IT teams managing researchers across multiple lab environments. Manual user provisioning in a platform that handles sensitive R&D data introduces compliance risks and delays researcher onboarding. When a scientist joins or leaves, IT must manually coordinate access across Benchling's complex permission structure for notebooks, entities, and workflows. For organizations with frequent collaborator access or seasonal research teams, this becomes unmanageable.

View full guide