SCIM Provisioning

Revspire supports SCIM 2.0 to automate the user and group lifecycle from your identity provider. Each SCIM connection is bound to one Revspire SSO provider and organization.

Supported Providers

Okta
OneLogin
Microsoft Entra ID
Any identity provider or provisioning client that supports SCIM 2.0 with HTTP Bearer authentication

Before You Start

Create and test the matching SAML provider in Revspire > Setup > SSO.
The Revspire organization must have an active Revspire Deal Room entitlement.
Have View SSO Settings, Edit SSO Providers, and Generate API Tokens permissions.
Either choose an active internal default profile or configure the identity provider to send a valid profileId or profileName.
For active provisioning, choose an eligible active default product with available license seats. Alternatively, provision users as inactive and assign a valid product in Revspire before activation.
Confirm the organization has valid timezone and currency defaults and one active internal Corporate role.

Configure SCIM in Revspire

Open Revspire > Setup > SSO.
Select the required SSO provider row and click SCIM Config.
Select and save the Default Profile For Provisioning unless the identity provider will send an explicit profile mapping.
Select and save the Default Product For Provisioning when users should be created active.
Copy the SCIM Base URL.
Click Generate Token and copy the token immediately. Revspire displays the token value only once.

SCIM Base URL = <copy from Revspire SSO > SCIM Config>
Authentication = HTTP Bearer token
Token = <copy when generated>

HTTP header form:
Authorization: Bearer <SCIM_TOKEN>

Generating or rotating a token expires the previous active token for that provider. Update the identity provider immediately after rotation.

Never reuse one provider’s token in another connector. A valid token always scopes requests to the provider that owns it, which can make the wrong provider’s resources appear missing.

Required User Mapping

userName = required, unique Revspire sign-in name
emails = required; the primary entry must be non-empty, or the first entry when none is primary
emails[type eq "work"].value = recommended governed work-email mapping
active = recommended boolean lifecycle state
externalId = recommended immutable identity-provider user ID
name.givenName = optional
name.familyName = optional
name.middleName = optional

For profile assignment, the recommended cross-provider setup is the Revspire default profile. Advanced clients can send profileId or profileName using urn:ietf:params:scim:schemas:extension:revspire:2.0:User. Product entitlement is managed in Revspire; the provider default supplies a product when one is required and no suitable retained assignment exists.

Supported Lifecycle

Users: create, list, read, replace, patch, and deactivate.
Groups: create, list, read, replace, patch, deactivate, and manage members.
DELETE deactivates Revspire users and groups rather than permanently deleting them.
Group members must be active users managed by the same provider-scoped SCIM connection.

Important Ownership and Uniqueness Rules

SCIM can list, read, and modify only users and groups owned by the same provider connection.
Existing manually created users are not automatically claimed by SCIM.
userName, email, and group display name are unique within the Revspire organization. externalId is unique within the provider connection.
A same-provider inactive group with the same external ID or display name can be reactivated; unrelated conflicts fail closed instead of overwriting records.
Plan an existing-user migration with your Revspire administrator before assigning a large production population.

Protocol Capabilities

PATCH = supported
Filtering = supported
Maximum page size = 200
Bulk operations = not supported
Password synchronization = not supported
Sorting = not supported
ETag concurrency = not supported