SCIM Provisioning
Current SCIM support for managed enterprise provisioning
SCIM provisioning support exists in Z8's enterprise auth stack, but the current product does not expose a dedicated self-serve SCIM setup page in admin settings.
Current Availability
Treat SCIM as a managed enterprise integration, not as a point-and-click configuration flow in the current UI.
If your organization needs SCIM, coordinate the rollout with the team responsible for your enterprise identity setup instead of expecting a full in-product onboarding wizard.
Organization Scope
SCIM provisioning is organization-scoped. It is meant to automate membership lifecycle changes for one organization at a time and does not imply cross-organization provisioning.
What The Current Integration Supports
When SCIM is enabled for an organization, the backend supports:
- Provisioning users into the current organization
- Updating user profile data from the identity provider
- Deactivating or reactivating access based on SCIM lifecycle events
- Applying default role-template behavior where that configuration has been set up
- Recording provisioning activity in SCIM-specific audit logs
The current implementation also supports org-scoped provisioning behavior such as auto-activation and deprovision handling, but those settings are not documented as a self-serve admin surface today.
Admin Expectations
- Do not expect a dedicated Settings page for SCIM setup in the current docs app or web app.
- Do not assume there is a user-facing flow that reveals an endpoint URL and bearer token inside the product today.
- Use the standard people-management pages, including Employee Management, to review the resulting members and employee records after provisioning is enabled.
Operational Notes
- SCIM is an enterprise integration and should be rolled out carefully per organization.
- Provisioned users may be auto-activated or may require follow-up review depending on the organization's configured behavior.
- Deprovisioning behavior can suspend access or deactivate the employee record depending on how the integration was configured.
Use Accurate Scope During Rollout
Keep SCIM planning focused on the current organization. Separate organizations need separate provisioning decisions and should not share assumptions about access or lifecycle behavior.