Summary and recommendation
Veeva PromoMats supports native SCIM 2.0 provisioning, but only on Enterprise plans with custom pricing (typically $50K+ annually for mid-size teams). The implementation requires significant technical expertise and costs $10K-$50K upfront. More problematic: Okta's official Veeva Vault connector supports SSO but explicitly excludes SCIM provisioning, forcing Okta customers to use third-party connectors like Aquera or build direct API integrations.
This creates a provisioning gap for life sciences teams who need automated user lifecycle management across their marketing operations. Without automated provisioning, IT teams manually manage user accounts in a system handling regulated promotional content—creating compliance risks and operational overhead. External users (agencies, partners) require special External license types with restricted permissions, adding complexity to manual provisioning workflows.
The strategic alternative
Veeva PromoMats 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? | No |
| SSO available? | Yes |
| SSO protocol | SAML 2.0 |
| Documentation | Not available |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | ✓ | ❌ | SSO only |
| 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 Veeva PromoMats accounts manually. Here's what that costs:
The Veeva PromoMats pricing problem
Veeva PromoMats gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Business | $50-200/user/mo | ||
| Enterprise | Custom |
Plan Structure
| Plan | Price | SCIM |
|---|---|---|
| Business | $50-200/user/mo | ❌ |
| Enterprise | Custom | ✓ |
Note: PromoMats pricing varies significantly within the Business tier based on feature requirements and user volume. Enterprise pricing is quote-based with implementation costs ranging $10K-$50K.
What this means in practice
Moving from Business to Enterprise for SCIM access creates substantial cost increases. Assuming mid-range Business pricing at $125/user/month and conservative Enterprise estimates:
| Team Size | Est. Annual Increase |
|---|---|
| 25 users | $75,000-150,000 |
| 50 users | $150,000-300,000 |
| 100 users | $300,000-600,000 |
These estimates reflect typical Enterprise premiums in life sciences platforms, plus mandatory implementation fees.
Additional constraints
Summary of challenges
- Veeva PromoMats 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
Veeva PromoMats doesn't sell SCIM à la carte. It's bundled with Enterprise plan features that start at custom pricing (typically $200K+ annually for mid-size life sciences teams):
The reality: most teams upgrading to Enterprise are paying for pharmaceutical-grade compliance features they may not need. If you're a smaller life sciences marketing team that just wants automated user provisioning, you're buying enterprise regulatory controls designed for global pharma companies.
Stitchflow Insight
We estimate ~60% of Enterprise features are overkill for teams that simply need automated user management without the full pharmaceutical compliance overhead.
What IT admins are saying
Community sentiment on Veeva PromoMats's SCIM implementation is mixed, with significant frustration around IdP compatibility and implementation complexity. Common complaints:
- Okta's official connector doesn't support SCIM provisioning despite Veeva having native SCIM
- Forced to use third-party solutions like Aquera for Okta provisioning
- Implementation costs ranging $10K-$50K on top of Enterprise licensing
- Complex external user management for agencies and partners
We have native SCIM but our Okta connector doesn't support it. Had to go with Aquera which added another vendor and cost layer.
The implementation was painful - lots of custom configuration needed for our agency partners. Took 6 months and $30K in professional services.
The recurring theme
Having native SCIM doesn't guarantee smooth provisioning - IdP connector limitations and complex implementation requirements create expensive workarounds for life sciences teams.
The decision
| Your Situation | Recommendation |
|---|---|
| Using Okta, need SCIM provisioning | Use Stitchflow: Okta connector doesn't support SCIM despite native availability |
| On Business plan, need user provisioning | Use Stitchflow: avoid the Enterprise upgrade and $10K-50K implementation |
| Already on Enterprise with SCIM budget | Use native SCIM: you're paying for the platform capability |
| Heavy external user management (agencies, partners) | Use Stitchflow: simpler than managing External license types and permissions |
| Small life sciences team, infrequent changes | Manual may work: but watch for compliance gaps in regulated environment |
The bottom line
Veeva PromoMats gates SCIM behind Enterprise. The upgrade may unlock provisioning, but the workflow still has to complete across the rest of your stack.
Close the Veeva PromoMats workflow gap
Veeva PromoMats 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
None
Key limitations
- SCIM 2.0 support introduced in Veeva Vault 18R2 release
- Okta connector does not support SCIM - requires Aquera or direct API
- Entra ID SCIM provisioning available for Vault Platform
- External users (agencies, partners) need External license type with limited permissions
- Implementation costs range from $10K-$50K
Documentation not available.
Configuration for Okta
Integration type
Okta Integration Network (OIN) app
Where to enable
Docs
Veeva Vault Okta connector supports SSO but does not currently support Veeva Vault's SCIM endpoint for user provisioning. Aquera connector available for provisioning.
Use Stitchflow for automated provisioning.
Configuration for Entra ID
Integration type
Microsoft Entra Gallery app with SCIM provisioning
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 Entra ID supports SCIM provisioning for Veeva Vault Platform. PromoMats is built on Vault platform and inherits SCIM capability.
Veeva PromoMats 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
Veeva PromoMats
Veeva PromoMats 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
