Summary and recommendation
Officevibe supports SCIM provisioning, but only through Okta's integration in the Okta Integration Network. While SCIM is included on paid plans starting at $5/user/month, the integration is limited to Okta users and requires navigating Workleap's API limitations—their underlying API "is based on SCIM but not fully SCIM compliant." For organizations using Microsoft Entra ID or Google Workspace, there's no native SCIM support, forcing IT teams to rely on manual CSV uploads or API workarounds.
This creates a significant gap for mixed-IdP environments or organizations planning to migrate from Okta. Employee engagement platforms like Officevibe see frequent user changes as teams grow and reorganize, making manual provisioning particularly burdensome. The 10-user minimum also means smaller teams pay for seats they don't use, while larger organizations face the operational overhead of maintaining custom provisioning workflows for non-Okta environments.
The strategic alternative
Officevibe gates SCIM behind Unknown. Skip the Unknown plan upgrade and automate complete outcomes across your stack. We maintain the integration layer underneath. You focus on judgment, not plumbing.
Quick SCIM facts
| SCIM available? | Yes |
| SCIM tier required | Unknown |
| 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 | ✓ | ❌ | 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 Officevibe accounts manually. Here's what that costs:
The Officevibe pricing problem
Officevibe gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Okta | ✓ | ||
| Microsoft Entra ID | ❌ | ||
| Google Workspace | ❌ |
Current SCIM Support
| Identity Provider | SCIM Support | Method |
|---|---|---|
| Okta | ✓ | Native SCIM via OIN |
| Microsoft Entra ID | ❌ | CSV upload only |
| Google Workspace | ❌ | Manual provisioning |
All paid plans ($5/user/month with 10-user minimum) include SCIM access where supported.
What this means in practice
For Okta customers: Full automation with user lifecycle management, group sync, and schema discovery. The integration supports Workleap's custom SCIM schema and includes group linking capabilities.
For Entra ID customers: No automated provisioning despite Officevibe being part of the broader Workleap suite. IT teams must manually upload CSV files through Workleap's API or rely on HRIS integrations to sync user data.
For mixed environments: Organizations using multiple IdPs face inconsistent provisioning experiences, with some users auto-provisioned while others require manual intervention.
Additional constraints
Summary of challenges
- Officevibe supports SCIM but only at Unknown 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
Officevibe includes SCIM provisioning with all paid plans starting at $5/user/month (10-user minimum). The upgrade from their free plan gets you:
The good news: SCIM isn't buried in an expensive enterprise tier. However, there's a catch - Workleap's API isn't fully SCIM compliant yet, and provisioning only works with Okta currently. No native Microsoft Entra ID or Google Workspace SCIM support exists.
If you're already investing in employee engagement tools, the $5/user price point is reasonable. But if you just need user provisioning for a simple feedback tool, you're paying for comprehensive HR tech features you may not need.
What IT admins are saying
Community sentiment on Officevibe's SCIM implementation is cautiously optimistic, though several practical limitations emerge in real-world deployments. Common complaints:
- Being locked into the Workleap ecosystem for full functionality
- Okta-only SCIM support excludes Microsoft Entra ID environments
- 10-user minimum creates budget pressure for smaller HR teams
- Workleap API isn't fully SCIM compliant, limiting integration flexibility
The Workleap API data model is based on SCIM but not fully SCIM compliant... you'll need to use CSV files or HRIS integration instead of direct Entra SCIM.
Group linking works well with Okta, but if you're on Microsoft you're basically stuck with manual provisioning or workarounds.
The recurring theme
While Officevibe offers decent SCIM functionality, the vendor lock-in to both Workleap's suite and Okta specifically limits deployment flexibility for mixed-IdP environments.
The decision
| Your Situation | Recommendation |
|---|---|
| Using Okta, want automated provisioning | Use native SCIM: Officevibe has full Okta integration with group linking |
| Using Entra ID or Google Workspace | Use Stitchflow: no native SCIM support for non-Okta IdPs |
| Need cross-platform Workleap suite provisioning | Use Stitchflow: manage all Workleap apps from one integration |
| Small team (<50), low turnover | Manual provisioning may work: but watch for onboarding delays |
| Budget-conscious, avoiding per-user costs | Use Stitchflow: flat $5K/year vs scaling user fees |
The bottom line
Officevibe offers solid SCIM provisioning but only through Okta, leaving Entra ID and Google Workspace customers without native automation. For multi-IdP environments or broader Workleap suite management, Stitchflow provides unified provisioning across all platforms.
Make Officevibe workflows AI-native
Officevibe gates SCIM behind Unknown. We build complete offboarding, user access reviews, and license workflows without that SCIM Tax upgrade.
Technical specifications
SCIM Version
2.0
Supported Operations
Create, Update, Deactivate, Groups
Supported Attributes
Not specifiedPlan requirement
Unknown
Prerequisites
SSO must be configured first
Key limitations
- Part of Workleap suite
- Group linking with Okta
- Schema discovery available
- Workleap API not fully SCIM compliant yet
- 10 user minimum on paid plans
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).
Officevibe in OIN with SCIM provisioning. Custom schema: urn:workleap:params:scim:schemas:extension:user:2.0:User. Group linking and schema discovery available.
Officevibe gates SCIM behind Unknown. Stitchflow automates complete workflows without that SCIM Tax upgrade.
Unlock SCIM for
Officevibe
Officevibe gates SCIM behind Unknown plan. We automate complete offboarding and access reviews across your stack without that SCIM Tax upgrade.
See how it works


