Stitchflow
Spekit logo

Spekit SCIM guide

Native SCIM

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

Native SCIM requires Basic/Premium plan

Summary and recommendation

Spekit supports SCIM provisioning, but only through Okta and only after you've already configured SAML SSO. The integration requires Premium or Enterprise pricing (starting at $20/user/month vs $10 for Basic), and you must contact Spekit Support to enable JIT provisioning. For a 100-person team, accessing automated provisioning means $24,000/year instead of $12,000 - a 100% price increase just to unlock basic user lifecycle management.

This creates a significant gap for IT teams using other identity providers like Entra ID, Google Workspace, or OneLogin. Without SCIM, you're stuck with manual user provisioning in a platform that typically needs to reach your entire sales and support organization. The compliance risk is real: departed employees retain access to customer data and internal processes until someone manually removes them from Spekit.

The strategic alternative

Spekit has native SCIM. Native SCIM is a start, but critical offboarding and access review workflows still break across systems. We maintain the integration layer underneath. You focus on judgment, not plumbing.

Quick SCIM facts

SCIM available?Yes
SCIM tier requiredEnterprise
SSO required first?Yes
SSO available?Yes
SSO protocolSAML 2.0
DocumentationOfficial docs

Supported identity providers

IdPSSOSCIMNotes
OktaOIN app with full provisioning
Microsoft Entra IDSSO only
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 Spekit accounts manually. Here's what that costs:

Source: Stitchflow aggregate data across apps with 2+ instances, normalized to 500 employees
Orphaned accounts (ex-employees with access)7
Unused licenses12
IT hours spent on manual management/year101 hours
Unused license cost/year$3,925
IT labor cost/year$6,088
Cost of compliance misses/year$1,741
Total annual financial impact$11,754

The Spekit pricing problem

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

Tier comparison

PlanPriceSSOSCIM
Basic$10/user/mo
Premium$20/user/mo
EnterpriseCustom

Plan Structure (Billed Annually)

PlanPriceSCIM
Basic$10/user/mo
Premium$20/user/mo
EnterpriseCustom

Note: SCIM requires SAML SSO setup first, then separate SCIM configuration. JIT provisioning is available but requires notifying Spekit Support.

What this means in practice

Using current list prices (Basic → Premium for SCIM access):

Team SizeAnnual Upgrade Cost
50 users+$6,000/year
100 users+$12,000/year
200 users+$24,000/year

Calculation: $10 upgrade per user × team size × 12 months

Add-ons like Product Guides increase costs further ($5/user/month), potentially reaching $15,000/year for a 50-person team with full features.

Additional constraints

Support dependency
SCIM setup requires coordination with Spekit Support after SAML configuration.
Two-step process
Must configure SAML SSO first, then separately enable SCIM provisioning.
Integration fees
Spekit now charges separate integration fees, adding to the total cost of ownership.
Limited IdP support
While Okta SCIM is documented, other identity providers may have limited or undocumented SCIM support.

Summary of challenges

  • Spekit supports SCIM but only at Enterprise tier (custom pricing)
  • 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

Spekit doesn't sell SCIM à la carte. It's bundled with Premium/Enterprise features:

SCIM automated provisioning (requires separate setup after SAML)
SAML single sign-on (SSO)
Just-in-time (JIT) provisioning (requires Support notification)
Product guides and in-app messaging ($5/user/mo add-on)
Advanced analytics and reporting
Priority customer support
Enhanced security controls

The reality: you're paying Premium pricing ($20/user/month) for a digital adoption platform when you may just need basic user provisioning. For a 50-person team, that's $12,000/year minimum—and integration fees are now charged separately on top of subscription costs.

Stitchflow Insight

We estimate ~60% of Premium features are irrelevant for teams that primarily need automated user management. The SCIM setup also requires manual coordination with Spekit Support, adding friction to what should be an automated process.

What IT admins are saying

Community sentiment on Spekit's SCIM implementation focuses on setup complexity and hidden costs. Common complaints:

  • SCIM requires separate configuration after SAML setup is complete
  • Must contact Spekit Support just to enable JIT provisioning
  • Integration fees are now charged separately from the base subscription
  • Premium tier requirement doubles the cost from Basic plans

Can get expensive for larger teams

G2 Review

Integration fees added

Community feedback on pricing changes

The recurring theme

While Spekit offers SCIM functionality, the manual setup process and additional fees create friction that undermines the automation benefits IT teams are seeking.

The decision

Your SituationRecommendation
On Basic ($10/user/mo), need SCIMUse Stitchflow: avoid the 2x price jump to Premium
On Premium, want to avoid Enterprise costsUse Stitchflow: get SCIM without tier upgrade
Already on Premium/Enterprise with SCIM includedUse native SCIM: you're paying for it
Need other Enterprise features beyond SCIMEvaluate Enterprise upgrade: SCIM comes bundled
Small team, low turnoverManual may work: but watch for security gaps

The bottom line

Spekit has native SCIM, but critical workflows still break across systems. Stitchflow builds complete end-to-end outcomes with your team.

Make Spekit workflows AI-native

Spekit has native SCIM, but critical workflows still break across systems. We build the full end-to-end workflow in your environment.

Works alongside native SCIM to close workflow gaps
Less than a week, start to finish (~2 hours of your time)
Built with your team; extend to anything else in the company
Book a Demo

Technical specifications

SCIM Version

2.0

Supported Operations

Create, Update, Deactivate, Groups

Supported Attributes

Not specified

Plan requirement

Enterprise

Prerequisites

SSO must be configured first

Key limitations

  • SCIM requires separate setup after SAML
  • Must notify Spekit Support for JIT provisioning
  • Integration fees now charged separately

Configuration for Okta

Integration type

Okta Integration Network (OIN) app with SCIM provisioning

Prerequisite

SSO must be configured before enabling SCIM.

Where to enable

Okta Admin Console → Applications → Spekit → Provisioning

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).

Okta SCIM for Spekit enables seamless user access, provisioning, and de-provisioning. Setup requires SAML first, then SCIM configuration.

Spekit has native SCIM, but critical workflows still break across systems. Stitchflow builds complete end-to-end outcomes with your team.

Unlock SCIM for
Spekit

Spekit has native SCIM, but complete workflows still span more than one tool. We build the full flow with your team so you can extend it to anything else in the company.

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

Last updated: 2026-01-11

* Pricing and features sourced from public documentation.

Keep exploring

Related apps

15Five logo

15Five

Has SCIM

Performance Management / Employee Engagement

SCIM StatusIncluded
Manual Cost$11,754/yr

15Five includes SCIM provisioning on all plans starting at $4/user/month, with full support for creating, updating, and deactivating users across Okta, Entra ID, Google Workspace, and OneLogin. However, 15Five's SCIM implementation has a critical prerequisite: SSO must be configured first, and their documentation explicitly warns against using JIT provisioning alongside SCIM due to duplicate user creation risks. This creates operational friction for IT teams managing performance management rollouts. The SSO-first requirement means you can't test SCIM provisioning in isolation, and the JIT conflict forces you to choose between automated onboarding convenience and reliable user lifecycle management. For HR-driven tools like 15Five that need to maintain accurate manager hierarchies and team structures, these provisioning gaps can disrupt performance review cycles and employee engagement tracking.

View full guide
Dropbox logo

Dropbox

Has SCIM
SCIM StatusIncluded
Manual Cost$11,754/yr

Dropbox Business supports SCIM 2.0 provisioning on Standard plans and above ($15/user/month), with solid integration across major identity providers including Okta, Azure AD, and Google Workspace. However, there's a critical architectural limitation: Dropbox Sign (formerly HelloSign) operates as a separate product that doesn't support SCIM at all, despite being a core part of many organizations' document workflows. This creates a significant provisioning gap for IT teams. While your main Dropbox storage accounts can be automatically managed, any users who need access to Dropbox Sign must be manually provisioned and deprovisioned. For organizations relying on both products, this means maintaining hybrid workflows where some users are automated and others require manual intervention—exactly the kind of inconsistency that leads to compliance issues and security gaps during employee transitions.

View full guide
Ramp logo

Ramp

Has SCIM

Corporate Cards / Expense Management

SCIM StatusIncluded
Manual Cost$11,754/yr

Ramp offers excellent native SCIM support across all plans, including their free tier. Users are automatically created, updated, and deactivated through standard SCIM protocols with major IdPs like Okta and Microsoft Entra. However, several operational limitations create gaps: SCIM deactivation doesn't actually delete users (they remain as "inactive"), corporate card termination requires manual intervention, and you can't run both SCIM and HRIS integrations simultaneously. These limitations matter most for financial compliance and offboarding workflows. When employees leave, their Ramp accounts stay in the system indefinitely, and any active corporate cards remain functional until manually terminated. For finance teams managing hundreds of users and cards, this creates audit trail concerns and potential security exposure from dormant accounts.

View full guide