Summary and recommendation
Reachdesk supports native SCIM provisioning, but only on Enterprise plans starting at $50,000/year. Teams on Business plans ($20,000/year) are locked out of automated provisioning entirely, despite paying substantial licensing fees. The pricing jump from Business to Enterprise represents a 2.5x increase—$30,000/year additional cost—often just to unlock user provisioning capabilities.
This creates a significant gap for mid-market teams who need automated user management but don't require Enterprise-level send volumes or global reach. Without SCIM, IT teams must manually provision and deprovision users in a high-stakes gifting platform that handles corporate spending and vendor relationships. SSO alone doesn't solve the lifecycle management challenge—deactivated employees could retain access to initiate sends and manage campaigns.
The strategic alternative
Reachdesk gates SCIM behind Contact Sales. 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 | Unknown |
| SSO required first? | No |
| SSO available? | Yes |
| SSO protocol | SAML 2.0 |
| Documentation | Not available |
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 Reachdesk accounts manually. Here's what that costs:
The Reachdesk pricing problem
Reachdesk gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Business | $20,000/yr (3 users, 1,500 sends) | ||
| Company | $35,000/yr (5 users, 4,000 sends) | ||
| Enterprise | $50,000/yr (10 users, 10,000 sends) |
Plan Structure
| Plan | Price | SCIM |
|---|---|---|
| Business | $20,000/yr (3 users, 1,500 sends) | ❌ |
| Company | $35,000/yr (5 users, 4,000 sends) | ❌ |
| Enterprise | $50,000/yr (10 users, 10,000 sends) | ✓ |
Note: All pricing shown is annual. Business and Company plans are limited to North America only; Enterprise is required for global sending capabilities.
What this means in practice
The jump to Enterprise for SCIM access represents a substantial cost increase:
| Current Plan | Upgrade Cost | Annual Impact |
|---|---|---|
| Business → Enterprise | +$30,000/year | 150% increase |
| Company → Enterprise | +$15,000/year | 43% increase |
This pricing model forces organizations to pay for expanded sending capacity and geographic reach even when they only need SCIM provisioning for their existing user base.
Additional constraints
Summary of challenges
- Reachdesk supports SCIM but only at Unknown tier ($50,000/yr (10 users, 10,000 sends))
- 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
Reachdesk requires Enterprise ($50,000/yr) for SCIM provisioning. It's bundled with global sending and advanced features:
The lower Business ($20,000/yr) and Company ($35,000/yr) plans are restricted to North America only. If you need global sending anyway, the Enterprise upgrade makes sense. If you just want automated user provisioning for a North America-only team, you're paying $30,000+ extra for geographic expansion you won't use.
Stitchflow Insight
Additionally, Reachdesk's SCIM implementation only works with Okta using their generic SCIM 2.0 template. There's no documented support for Microsoft Entra ID or other identity providers. We estimate ~60% of Enterprise features are irrelevant for teams that only need basic SCIM provisioning.
What IT admins are saying
Community sentiment on Reachdesk's SCIM implementation reveals mixed reactions about their Okta-only approach and enterprise pricing requirements.
- SCIM provisioning only works through Okta using a generic template
- No Microsoft Entra ID integration despite widespread enterprise usage
- Forced to reach Enterprise tier ($50K/year) just for automated provisioning
- Geographic restrictions on lower tiers (Business/Company plans North America only)
We're an Entra shop and there's literally no way to get automated provisioning working. Had to stick with manual user management.
The jump from Company ($35K) to Enterprise ($50K) just for SCIM feels excessive when we only need basic user sync.
The recurring theme
Reachdesk's SCIM is locked behind their highest tier and only works with Okta, leaving Microsoft-heavy organizations without automated provisioning options.
The decision
| Your Situation | Recommendation |
|---|---|
| On Business plan, need SCIM | Use Stitchflow: avoid the $30K jump to Enterprise |
| Enterprise budget but need Entra/Google integration | Use Stitchflow: native SCIM only works with Okta |
| Already on Enterprise with Okta | Use native SCIM: you're paying $50K+ already |
| Global team needing worldwide sending | Evaluate Enterprise: SCIM comes with required global features |
| Small marketing team, low user turnover | Manual may work: but watch for campaign delays from access gaps |
The bottom line
Reachdesk gates SCIM behind Contact Sales. The upgrade may unlock provisioning, but the workflow still has to complete across the rest of your stack.
Close the Reachdesk workflow gap
Reachdesk gates SCIM behind Contact Sales, 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
Unknown
Prerequisites
None
Key limitations
- SCIM provisioning via Okta using generic SCIM 2.0 template
- JIT provisioning also available via SAML
- Business/Company plans limited to North America
- Enterprise required for global sending (US, Canada, UK, EU, APAC)
Documentation not available.
Configuration for Okta
Integration type
Okta Integration Network (OIN) app with SCIM provisioning
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).
Docs
Full SCIM support: auto-create users, auto-deactivate, update user info, team management via group push. Users default to 'sender' role. Uses SCIM 2.0 Test App (OAuth Bearer Token) template.
Reachdesk gates SCIM behind Contact Sales. The upgrade may unlock provisioning, but the workflow still has to complete across the rest of your stack.
Close the workflow gap in
Reachdesk
Reachdesk gates SCIM behind Contact Sales plan. That can unlock provisioning, but it still does not complete the offboarding, access review, or license workflow across your stack, and it can add a 150% markup just to get there.
Start with the free gap diagnostic
