Skip to main content
Velor

Enterprise IT guides

SCIM user provisioning

Create, update and deactivate Velor users from your identity provider, with immediate session revocation on deprovisioning.

Who can do this: the workspace owner, from /dashboard/settings/scim (SCIM provisioning; also linked from the SSO page).

1. Make a token

Press Generate under Generate new SCIM token, give it a description (for example "Okta production"), and copy the token now: it begins velor_scim_ and is shown once; Velor stores only a hash. You can revoke a token from the same page (the Revoke SCIM token control). Generating and revoking are recorded in your audit log (org.scim_token_generated, org.scim_token_revoked).

2. Point your identity provider at Velor

Base URL (also shown on the page): https://app.velorplatforms.com/api/scim/v2. Authentication is a Bearer token: the token from step 1.

3. What is supported

ResourceOperations
Userslist and filter (userName eq "<email>", externalId eq "<id>"), get, create, replace (PUT), update (PATCH), delete
Groupsaccepted so your IdP's flow completes, but groups are not stored: Velor has no groups to map yet
ServiceProviderConfig, Schemasdiscovery

Not supported: bulk operations, sorting, ETags, password changes. Filtering returns at most 200 results.

Attributes Velor reads: userName (must be an email address; when SSO is configured it must be on the SSO domain), active, displayName / name (formatted, givenName, familyName), and roles[0].value. A role of admin creates an admin; any other role value creates a member. Velor never assigns owner through SCIM.

4. Deprovisioning: what actually happens

When your IdP sends active: false (PUT or PATCH):

  1. The event is written to your audit log first (scim.user_deactivated).
  2. All of the user's sessions are revoked immediately.
  3. The user is banned from signing in by any method (password, magic link, SSO) until your IdP sends active: true, which lifts the ban.

A SCIM DELETE writes the audit record, revokes sessions, then deletes the user. Deactivation (403) and deletion (409) both refuse the owner; changing the owner's role is refused (403); demoting or deleting the last admin or owner is refused (409). An IdP misconfiguration therefore cannot remove the workspace's owner.

Requests are rate limited per workspace; if the limiter itself is unavailable, requests are refused rather than allowed.

Troubleshooting

Symptom at the IdPCause
401 on every callToken mistyped, revoked, or from another workspace
404 on every callThe URL is missing /api (the base URL above is exact)
400 "userName must be an address on <domain>"SSO is configured and the user's address is outside the SSO domain
409 "cannot delete the last admin/owner" or "cannot demote the last admin/owner"Intended protection; add another admin first
403 "cannot deprovision owner via SCIM"The owner cannot be deactivated by the IdP; transfer ownership first (Settings, Team)

In the product: /dashboard/settings/scim (sign-in required).