Summary and recommendation
GetAccept supports SCIM provisioning for automated user management, but only on Enterprise plans with custom pricing. This creates a significant barrier for sales teams on the more affordable eSign ($25/user/month) or Professional plans ($39-79/user/month) who need automated provisioning as they scale their digital sales operations.
The pricing gap is substantial. Moving from eSign to Enterprise represents a major cost increase that's often unjustifiable just to unlock provisioning automation. For growing sales teams, this creates a manual user management burden precisely when they need efficiency most—during rapid hiring cycles or territory reorganizations where sales reps need immediate access to close deals.
The strategic alternative
GetAccept 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 | Not available |
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 GetAccept accounts manually. Here's what that costs:
The GetAccept pricing problem
GetAccept gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Plan Structure
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| eSign | $25/user/mo | ||
| DealRoom Professional | $39/user/mo | ||
| ContractRoom Professional | $49/user/mo | ||
| FullSuite Professional | $79/user/mo | ||
| Enterprise | Custom |
Note: Professional+ plans require annual billing. Only Enterprise includes SAML SSO and SCIM provisioning.
What this means in practice
Since Enterprise pricing is custom, expect significant cost increases over the $79/user/month FullSuite Professional plan. Based on typical SaaS enterprise pricing patterns:
| Team Size | Estimated Annual Impact |
|---|---|
| 25 sales reps | $35,000+ additional cost |
| 50 sales reps | $70,000+ additional cost |
| 100 sales reps | $140,000+ additional cost |
These estimates assume Enterprise pricing at ~$150-200/user/month, which is common for custom enterprise tiers.
Additional constraints
Summary of challenges
- GetAccept 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
GetAccept doesn't sell SCIM à la carte. It's bundled with Enterprise features that most sales teams don't need:
Stitchflow Insight
If you need enterprise-grade security controls anyway, the upgrade may make sense. If you just want automated user provisioning for your sales team, you're paying for a bundle you won't fully use. We estimate ~60% of Enterprise features are irrelevant for teams that only need SCIM to manage sales rep access to documents and deals.
What IT admins are saying
Community sentiment on GetAccept's Enterprise-only SCIM is mixed, with cost concerns overshadowing implementation satisfaction. Common complaints:
- Enterprise pricing requirements that force expensive upgrades just for user provisioning
- Lack of transparent pricing makes budget planning difficult
- Having to pay for advanced features when you only need basic SCIM automation
- Limited flexibility for mid-market teams that need provisioning but not full Enterprise features
We're a 50-person sales team and just need automated user provisioning. The jump to Enterprise feels excessive for what should be a basic security feature.
GetAccept's SCIM works well once you're on Enterprise, but getting there requires a custom quote conversation that takes weeks.
The recurring theme
GetAccept gates essential identity automation behind Enterprise pricing, creating budget friction for teams that need SCIM but don't require the full Enterprise feature set.
The decision
| Your Situation | Recommendation |
|---|---|
| On Professional/Deal Room, need SCIM | Use Stitchflow: avoid the Enterprise tier jump |
| Already on Enterprise plan | Use native SCIM: you're paying for it already |
| Need Enterprise features beyond SCIM | Evaluate Enterprise: SCIM comes bundled with other features |
| Small sales team, low rep turnover | Manual may work: but watch for document access gaps |
| Mixed IdP environment or complex provisioning | Use Stitchflow: broader IdP support and managed automation |
The bottom line
GetAccept gates SCIM behind Enterprise. The upgrade may unlock provisioning, but the workflow still has to complete across the rest of your stack.
Close the GetAccept workflow gap
GetAccept 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
- Enterprise plan required
- SCIM for user provisioning
Documentation not available.
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).
Docs
SAML 2.0 SSO and SCIM provisioning. Each entity requires separate Okta app. Provisions users and teams. Supports user create, update, delete/inactivate, team management, role-based access. Name ID format must be EmailAddress.
GetAccept 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).
Azure AD SCIM provisioning supported. Creates users, updates attributes, deletes/inactivates users, creates teams from AD groups, manages group membership, supports custom application roles for access rights.
GetAccept 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
GetAccept
GetAccept 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
