Skip to main content
SCIM (System for Cross-domain Identity Management) lets your identity provider (IdP) automatically create, update, and deactivate users in Probo. When a new employee joins your company or someone leaves, Probo reflects those changes without any manual work.

How SCIM works in Probo

  • Create user — When you assign a user to the Probo app in your IdP, Probo creates their profile and membership automatically.
  • Update user — Changes to a user’s name, title, department, or other attributes in your IdP are synced to Probo.
  • Deactivate user — Removing a user from the Probo app in your IdP deactivates their Probo profile and revokes access.
SCIM only manages users provisioned through SCIM. Users created manually or via SAML SSO are not affected by SCIM sync operations.

Before you start

  • You need the Owner role in your Probo organization.
  • Your identity provider must support SCIM 2.0 (Okta, Azure AD, Google Workspace, JumpCloud, and most enterprise IdPs do).

Setting up SCIM

1

Create the SCIM configuration

Navigate to SettingsSecurityProvisioning and click Enable SCIM.Probo generates a SCIM token and displays your SCIM endpoint URL. Copy both — the token is only shown once.
2

Note your SCIM endpoint

Your SCIM base URL is:
https://app.getprobo.com/api/connect/v1
Enter this as the SCIM base URL in your identity provider.
3

Configure your identity provider

In your IdP’s SCIM integration settings, enter:
SettingValue
SCIM base URLhttps://app.getprobo.com/api/connect/v1
Authentication methodHTTP Header
Authorization headerBearer <your-scim-token>
Supported operationsCreate, Update, Deactivate
Refer to your IdP’s documentation for exact configuration steps.
4

Assign users

In your IdP, assign the users or groups you want to provision to the Probo application. The IdP will push those users to Probo immediately.

Supported SCIM attributes

Probo accepts the following SCIM user attributes:
SCIM attributeProbo profile field
userNameUsername
displayNameFull name
emails[primary].valueEmail address
activeProfile state (active / inactive)
titlePosition
userTypeProfile kind
name.givenNameGiven name
name.familyNameFamily name
nickNameNickname
localeLocale
timezoneTimezone
preferredLanguagePreferred language
enterprise.employeeNumberEmployee number
enterprise.departmentDepartment
enterprise.costCenterCost center
enterprise.organizationEnterprise organization
enterprise.divisionDivision
enterprise.manager.valueManager reference
Enterprise attributes use the standard SCIM extension schema: urn:ietf:params:scim:schemas:extension:enterprise:2.0:User.

Regenerating the SCIM token

If your SCIM token is compromised or you need to rotate it:
1

Open provisioning settings

Navigate to SettingsSecurityProvisioning.
2

Regenerate the token

Click Regenerate token. The old token is immediately invalidated.
3

Update your identity provider

Replace the old token with the new one in your IdP’s SCIM configuration.
Regenerating the token invalidates the old one immediately. SCIM sync from your IdP will fail until you update the token in your IdP’s settings.

SCIM bridge for Google Workspace

If you use Google Workspace, Probo supports a SCIM bridge that syncs your directory automatically without requiring Google Workspace’s native SCIM support. To configure the SCIM bridge:
  1. Connect your Google Workspace account under SettingsIntegrationsGoogle Workspace.
  2. Navigate to SettingsSecurityProvisioningBridge.
  3. Optionally, add usernames to the Excluded usernames list to prevent those accounts from being synced.
The bridge runs in the background and keeps your Probo user directory in sync with Google Workspace.

SCIM events log

Every SCIM request your identity provider makes to Probo is logged. Use the events log to troubleshoot provisioning issues.
1

Open the events log

Navigate to SettingsSecurityProvisioningEvents.
2

Review events

Each entry shows:
FieldDescription
MethodHTTP method (POST, PUT, PATCH, DELETE)
PathSCIM resource path (e.g. /Users/...)
Status codeHTTP response code
UsernameThe user the operation targeted
IP addressSource IP of the IdP request
Error messageDetails if the operation failed
TimestampWhen the event occurred
A 409 Conflict status on a POST /Users request usually means the user already exists in Probo. A 401 Unauthorized means your SCIM token is incorrect or has been regenerated.

Deleting the SCIM configuration

To remove SCIM provisioning, navigate to SettingsSecurityProvisioning and click Delete configuration. Existing users provisioned via SCIM remain in Probo but will no longer be synced.

SSO with SAML

Combine SCIM provisioning with SAML single sign-on.

Roles and permissions

Understand what each role can do in Probo.

Build docs developers (and LLMs) love