Summary and recommendation
DocuSign supports SCIM provisioning, but only with Enterprise Edition accounts at custom pricing. For teams on Standard ($25-45/user/month) or Business Pro ($40-65/user/month) plans, there's no automated user provisioning available—forcing manual account creation and lifecycle management for every user.
This creates a significant operational burden for IT teams managing DocuSign access. Without SCIM, you're manually onboarding users, updating permissions, and offboarding departing employees. Given DocuSign's critical role in contract workflows, manual processes increase the risk of access remaining active after termination or users getting incorrect permission levels. The activation email requirement adds another friction point, as provisioned users must complete setup themselves rather than having accounts ready immediately.
The strategic alternative
Docusign gates SCIM behind Enterprise. 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 | Enterprise |
| SSO required first? | Yes |
| SSO available? | Yes |
| SSO protocol | SAML 2.0 |
| Documentation | Official docs |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | ✓ | ✓ | OIN app with full provisioning |
| Microsoft Entra ID | ✓ | ✓ | Gallery app with SCIM |
| 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 Docusign accounts manually. Here's what that costs:
The Docusign pricing problem
Docusign gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Plan Structure
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Personal | $10-15/user/mo | ||
| Standard | $25-45/user/mo | ||
| Business Pro | $40-65/user/mo | ||
| Enterprise | Custom pricing |
Note: SAML SSO also requires Enterprise tier plus a one-time activation fee on top of the custom pricing.
What this means in practice
The forced Enterprise upgrade creates unpredictable costs since DocuSign doesn't publish Enterprise pricing. Based on typical SaaS pricing patterns, organizations often see:
For teams currently on Business Pro at $65/user/month, the Enterprise upgrade typically represents a 50-100% increase in per-user costs.
Additional constraints
Summary of challenges
- Docusign 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
DocuSign doesn't sell SCIM separately. It's bundled with Enterprise Edition features:
Additionally, DocuSign charges a separate one-time activation fee for SAML on top of the already-custom Enterprise pricing, and their SCIM implementation has notable limitations like restricted permission profile support with certain IdPs and mandatory user activation emails.
Stitchflow Insight
The Enterprise tier is designed for large organizations with complex compliance needs. If you just need automated user provisioning, you're paying for enterprise-grade features like custom workflows, advanced analytics, and dedicated support that most teams won't use. We estimate ~80% of Enterprise features are irrelevant for organizations that simply want to automate user lifecycle management.
What IT admins are saying
Community sentiment on DocuSign's SCIM implementation reveals frustration with enterprise-only access and complex configurations. Common complaints:
- Being locked into expensive enterprise pricing just for automated provisioning
- One-time activation fees on top of already premium enterprise costs
- Limited permission profile support with certain IdPs like CyberArk
- Separate SCIM configurations required for eSignature vs CLM products
The enterprise requirement plus activation fee feels like double-dipping on what should be basic identity management functionality.
Having to configure SCIM separately for eSignature and CLM is a nightmare - it's the same company, same users, but completely different admin consoles.
The recurring theme
DocuSign gates essential identity automation behind enterprise pricing while adding complexity through separate product configurations and additional fees.
The decision
| Your Situation | Recommendation |
|---|---|
| Not on Enterprise, need SCIM | Use Stitchflow: avoid the expensive tier jump to custom Enterprise pricing |
| On Business Pro, satisfied with features | Use Stitchflow: get SCIM without upgrading from $40-65/user/month |
| Already on Enterprise | Use native SCIM: you're paying for it anyway |
| Need Enterprise features beyond SCIM | Evaluate Enterprise upgrade: SCIM comes bundled with other advanced features |
| Small team, low employee turnover | Manual may work: but watch for user activation friction and security gaps |
The bottom line
Docusign gates SCIM behind Enterprise. The upgrade may unlock provisioning, but the workflow still has to complete across the rest of your stack.
Close the Docusign workflow gap
Docusign gates SCIM behind Enterprise, 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
Enterprise
Prerequisites
SSO must be configured first
Key limitations
- SAML requires Enterprise Edition + one-time activation fee
- CyberArk provisioning only works with 3 default permission profiles
- User activation email sent on provisioning - user must complete activation
Configuration for Okta
Integration type
Okta Integration Network (OIN) app with SCIM provisioning
Prerequisite
SSO must be configured before enabling SCIM.
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).
Full SCIM provisioning with group linking and schema discovery. Configure API Account ID in Okta. Can assign permission profiles (Viewer, Sender, Admin). Also available: DocuSign by Aquera connector for advanced LCM.
Docusign gates SCIM behind Enterprise. The upgrade may unlock provisioning, but the workflow still has to complete across the rest of your stack.
Configuration for Entra ID
Integration type
Microsoft Entra Gallery app with SCIM provisioning
Prerequisite
SSO must be configured before enabling SCIM.
Where to enable
Required credentials
Tenant URL (SCIM endpoint) and Secret token (bearer token from app admin console).
Configuration steps
Set Provisioning Mode = Automatic, configure SCIM connection.
Provisioning trigger
Entra provisions based on user/group assignments to the enterprise app.
Sync behavior
Entra provisioning runs on a scheduled cycle (typically every 40 minutes).
Automatic user provisioning supported. Requires paid production account with enterprise plan. Note: Group provisioning not supported, only users. Does not work with Developer Sandbox - production only.
Docusign gates SCIM behind Enterprise. The upgrade may unlock provisioning, but the workflow still has to complete across the rest of your stack.
Close the workflow gap in
Docusign
Docusign gates SCIM behind Enterprise plan. That can unlock provisioning, but it still does not complete the offboarding, access review, or license workflow across your stack.
Start with the free gap diagnostic
