System for Cross-domain Identity Management (SCIM) is a standard protocol that enables automated user provisioning and deprovisioning for identity providers. Once enabled, your identity provider will take over user lifecycle management, from onboarding and updates to deactivation, and your staff member will be able to log in using Single Sign On.
This guide walks you through how to enable SCIM for your organisation.
Prerequisites
Admin access to your Identity Provider (IdP)
Step 1: Contact our support team to request your SCIM Credentials
You will be provided with a SCIM Base URL and Token. Ensure you store these credentials securely.
Step 2: Configure SCIM in your identity provider
For Okta:
Go to your Okta Admin Dashboard.
Navigate to Applications > Select your app > Provisioning tab.
Click Configure API Integration.
Paste the SCIM Base URL and Bearer Token from your product.
Test the connection and save.
For Azure AD:
Go to Enterprise Applications > Select your app.
Under Provisioning, set the mode to Automatic.
Enter the SCIM endpoint and credentials.
Test and save the configuration.
Step 3: Map SCIM Attributes
Most identity providers allow you to configure how user data is mapped to your product. Common attributes include:
userName → email
name.givenName → first name
name.familyName → last name
emails[type eq "work"].value → work email
Step 4: Test Provisioning
Create a user in your IDP.
See if they can sign up
Update user attributes such as name.
Check if the updates are reflected within the application.
Deactivate User.
1. The user should no longer be able to access their Silent Push account.