Summary and recommendation
Grammarly supports SCIM provisioning on Pro plans ($12/user/month annually), but with a critical prerequisite: SAML SSO must be enabled first. This creates an unnecessary dependency where you can't automate user provisioning without also implementing single sign-on. Additionally, group provisioning is only available on Enterprise plans and requires a manual request - meaning you can't automatically assign users to specific style guides or team configurations through your IdP.
This SAML-first approach creates operational friction for IT teams who want automated provisioning but aren't ready for full SSO deployment. You're forced to implement both systems simultaneously, increasing complexity and potential failure points. Without automated group provisioning, teams lose access to proper style guides and organizational controls, defeating much of the purpose of centralized management.
The strategic alternative
Stitchflow provides SCIM-level provisioning through resilient browser automation for Grammarly without requiring SAML SSO implementation or Enterprise upgrades. Works with any Grammarly plan and any IdP (Okta, Entra, Google Workspace, OneLogin). Flat pricing under $5K/year, regardless of team size.
Quick SCIM facts
| SCIM available? | Yes |
| SCIM tier required | Business |
| 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 Grammarly accounts manually. Here's what that costs:
The Grammarly pricing problem
Grammarly gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Plan Structure (Per User, Billed Annually)
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Free | $0 | ||
| Pro | $12/user/mo | ||
| Enterprise | Custom pricing |
Note: SCIM is available starting with Pro, but SAML SSO must be configured before SCIM can be enabled. Group provisioning requires Enterprise tier and must be requested separately.
What this means in practice
For teams currently on Free or considering Grammarly adoption:
| Team Size | Pro Plan Cost | Enterprise Premium |
|---|---|---|
| 50 users | $7,200/year | Custom (typically 2-3x Pro) |
| 100 users | $14,400/year | Custom (typically 2-3x Pro) |
| 200 users | $28,800/year | Custom (typically 2-3x Pro) |
Calculation: $12 × users × 12 months for Pro tier access
Additional constraints
Summary of challenges
- Grammarly supports SCIM but only at Business tier (Custom pricing (unlimited AI credits, style guides))
- 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
Grammarly doesn't sell SCIM standalone. It's bundled with Pro/Enterprise features:
Enterprise customers also face the limitation that group provisioning requires a special request - it's not automatically available even at the highest tier.
Stitchflow Insight
The SAML SSO prerequisite means you're forced into identity management features whether you want them or not. For teams that just need automated user provisioning, you're paying for writing enhancement features that may be overkill. We estimate ~60% of Pro/Enterprise features are focused on advanced writing capabilities rather than identity management.
What IT admins are saying
Community sentiment on Grammarly's SCIM implementation is mixed, with specific friction points around prerequisites and feature restrictions:
- Requiring SAML SSO to be configured before SCIM can be enabled
- Group provisioning locked behind Enterprise tier and requiring special requests
- Token management complexity with certain IdP configurations
- Confusion around the Pro vs. Enterprise feature differences
Why do I need to set up SAML first just to get SCIM working? Most other apps let you do SCIM independently.
Group provisioning 'available upon request' for Enterprise feels like artificial gatekeeping for a standard SCIM feature.
The recurring theme
While Grammarly's SCIM starts at the Pro level ($12/user/month), the SSO prerequisite and Enterprise-only group provisioning create unnecessary implementation hurdles for straightforward user lifecycle automation.
The decision
| Your Situation | Recommendation |
|---|---|
| On Pro plan, need SCIM provisioning | Use Stitchflow: avoid the Enterprise upgrade and SSO prerequisite |
| Have Enterprise but struggling with SCIM setup | Use Stitchflow: skip the SSO requirement and complex token management |
| Need group provisioning for team management | Use Stitchflow: avoid Enterprise upgrade and manual request process |
| Already on Enterprise with working SCIM | Use native SCIM: you're paying for it and have the prerequisites |
| Small team with low turnover | Manual may work: but watch for seat licensing waste and access gaps |
The bottom line
Grammarly's SCIM requires both Pro/Enterprise pricing and SAML SSO as a prerequisite, creating barriers for teams that just want automated user provisioning. For organizations that need SCIM without the SSO complexity or Enterprise upgrade, Stitchflow delivers the automation at a flat rate.
Automate Grammarly without the tier upgrade
Stitchflow delivers SCIM-level provisioning through resilient browser automation, backed by 24/7 human in the loop for Grammarly at <$5K/year, flat, regardless of team size.
Technical specifications
SCIM Version
2.0
Supported Operations
Create, Update, Deactivate, Groups
Supported Attributes
Not specifiedPlan requirement
Business
Prerequisites
SSO must be configured first
Key limitations
- SAML SSO must be enabled before SCIM
- Group provisioning only for Enterprise (upon request)
- CostCenter attribute mapping 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).
Full SCIM 2.0 provisioning. Supports create, update, deactivate users. Group provisioning available for Enterprise upon request. CostCenter attribute mapping supported.
Native SCIM is available on Business. Use Stitchflow if you need provisioning without the tier upgrade.
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).
Full SCIM 2.0 provisioning. SAML SSO must be enabled before SCIM. User accounts created and onboarding emails sent when assigned in IdP.
Native SCIM is available on Business. Use Stitchflow if you need provisioning without the tier upgrade.
Unlock SCIM for
Grammarly
Grammarly gates automation behind Business/Enterprise plan. Stitchflow delivers the same SCIM outcomes for a flat fee.
See how it works
