Summary and recommendation
Peakon (now Workday Peakon Employee Voice) supports SCIM 2.0 for automated user provisioning, but only on Enterprise plans starting at $20,000/year. While the SCIM implementation covers core user lifecycle operations (create, update, deactivate), it notably excludes group synchronization—meaning you can't automatically manage survey groups, department segments, or role-based access through your identity provider.
This creates a significant operational gap for IT teams. Employee engagement platforms like Peakon rely heavily on proper user segmentation for meaningful survey targeting and analytics. Without group sync, admins must manually maintain organizational structures within Peakon every time someone changes departments, roles, or managers. For organizations with frequent headcount changes or complex hierarchies, this becomes a time-consuming maintenance burden that defeats the purpose of automated provisioning.
The strategic alternative
Peakon gates SCIM behind Enterprise (starting $20,000/year). 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 Peakon accounts manually. Here's what that costs:
The Peakon pricing problem
Peakon gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Standard | Starting at $20,000/year | ||
| Enterprise | Custom pricing |
Plan Structure
| Plan | Price | SCIM |
|---|---|---|
| Standard | Starting at $20,000/year | ❌ |
| Enterprise | Custom pricing | ✓ |
Note: Peakon's pricing is based on organization size with custom quotes required for Enterprise access. The platform is now part of the Workday ecosystem, which influences both pricing and integration capabilities.
What this means in practice
The jump from Standard to Enterprise represents a substantial cost increase that many organizations find prohibitive:
For a typical 500-person organization, the Enterprise upgrade can easily add $30,000-50,000+ annually over Standard pricing.
Additional constraints
Summary of challenges
- Peakon 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
Peakon doesn't sell SCIM separately. It's bundled into their Enterprise offering, which starts at $20,000/year:
Note: Group sync isn't supported via SCIM, even at the Enterprise level. You'll need to manage team assignments manually in Peakon's admin console.
Stitchflow Insight
The core value is employee engagement surveys and analytics. If you need these HR capabilities anyway, the Enterprise upgrade delivers comprehensive functionality. If you just want automated user provisioning for a simpler feedback tool, you're paying enterprise prices for features most IT teams won't use. We estimate ~60% of Enterprise features are HR-specific and irrelevant for teams that only need identity management.
What IT admins are saying
Community sentiment on Peakon's SCIM implementation is mixed, with frustrations centered around limitations and enterprise requirements. Common complaints:
- No group sync support via SCIM despite full 2.0 implementation
- High minimum pricing ($20,000/year) that excludes smaller organizations
- Workday ecosystem lock-in for optimal integration experience
- Custom attributes requiring extension schema configuration
For Azure AD, only sync /Users/ not /Groups/ - this creates a lot of manual work for managing access controls.
High cost compared to some employee feedback tools, especially when you factor in the enterprise requirement just to get SCIM.
The recurring theme
While Peakon offers solid SCIM 2.0 user provisioning, the lack of group management and high enterprise pricing threshold creates operational gaps that force admins into workarounds or expensive upgrades.
The decision
| Your Situation | Recommendation |
|---|---|
| Need SCIM but don't have $20K+ budget | Use Stitchflow: start with a free gap diagnostic, then build the workflow across every app without asking your team to own the plumbing. |
| Already paying for Workday Peakon Enterprise | Use native SCIM: you're paying for it anyway |
| Need group provisioning alongside users | Use Stitchflow: native SCIM doesn't support groups |
| Small HR team, infrequent employee changes | Manual may work: but watch for security gaps |
| Considering alternatives to avoid high costs | Evaluate competitors: Culture Amp, 15Five offer lower entry points |
The bottom line
Peakon gates SCIM behind Enterprise (starting $20,000/year). The upgrade may unlock provisioning, but the workflow still has to complete across the rest of your stack.
Close the Peakon workflow gap
Peakon gates SCIM behind Enterprise (starting $20,000/year), 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
- Groups not supported via SCIM
- Part of Workday ecosystem
- For Azure AD, only sync /Users/ not /Groups/
- Custom user attributes require extension schema
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 support for user provisioning. Enable Employee Provisioning in Peakon admin before configuring Okta. Custom attributes can be synced (department, manager, DOB).
Peakon gates SCIM behind Enterprise (starting $20,000/year). 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).
Microsoft official tutorial available. Only sync /Users/ - Groups not supported. Custom attributes via urn:ietf:params:scim:schemas:extension:peakon:2.0:User extension.
Peakon gates SCIM behind Enterprise (starting $20,000/year). The upgrade may unlock provisioning, but the workflow still has to complete across the rest of your stack.
Close the workflow gap in
Peakon
Peakon gates SCIM behind Enterprise (starting $20,000/year) 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
