PushizoDocs
Security & compliance

Member provisioning with SCIM 2.0

Your identity provider (Okta, Microsoft Entra ID, OneLogin, JumpCloud…) automatically adds Pushizo members, updates their roles and removes those who leave via SCIM 2.0. SCIM is on the Enterprise plan and is used together with SSO…

Your identity provider (Okta, Microsoft Entra ID, OneLogin, JumpCloud…) automatically adds Pushizo members, updates their roles and removes those who leave via SCIM 2.0. SCIM is on the Enterprise plan and is used together with SSO (SSO guide, docs/adr/0023-kurumsal-kimlik-sso-scim-jwt.md §8).

Setup

  1. Create a token under Organization → Security & SSO → SCIM provisioning. The token (scim_…) is shown only once.
  2. Enter the following in your IdP's SCIM settings:
    • SCIM base URL: https://<API>/scim/v2
    • Authentication: HTTP Header / Bearer token → the token you created
    • Unique identifier: userName (email)
  3. The users' email domain must be verified in the organization; otherwise creation returns 400 invalidValue.

Supported operations

ResourceOperations
/UsersGET (filter: userName eq "…", externalId eq "…"; startIndex, count), POST, GET /{id}, PUT /{id}, PATCH /{id} (active, name, displayName, externalId), DELETE /{id}
/GroupsGET (filter: displayName eq "…"), POST, GET/PUT/PATCH/DELETE /{id} (add/remove members; Entra ID members[value eq "…"] format)
/ServiceProviderConfig, /ResourceTypes, /SchemasDiscovery

Responses use application/scim+json, and errors are returned with the RFC 7644 error schema.

Behavior

  • Creation: if the account doesn't exist, it is created without a password (login is via SSO), and the membership is added with the default role of the first SSO connection. The member quota and the plan's role gate apply.
  • Deactivation / deletion (active: false or DELETE): the membership is removed and the user's sessions for this organization are closed. The organization owner cannot be removed via SCIM.
  • Groups → role: if the group name exists in the group → role mapping of the SSO connection, its members get that role; across multiple groups, the most privileged role applies. Groups without a mapping do not change the role.
  • userName (email) cannot be changed: accounts are shared across organizations (400 mutability).

Security

Tokens are stored only as SHA-256 digests, can be revoked from the dashboard, and show their last-used time. A token can only see and modify members of its own organization.

On this page