Configure SCIM Provisioning
Sync users, groups, and profile attributes from an identity provider.
Use SCIM when your identity provider should automatically create, update, or deactivate users.
Before you begin
You need:
- Admin access to authentication settings.
- Identity provider admin access.
- Agreement that the IdP owns user lifecycle or group membership.
- A secure place to store the SCIM token.
- A pilot user or group for testing.
Manual changes to synced fields or groups can be overwritten by the source system.
Enable SCIM
- Open Authentication > SCIM.
- Turn on Enable SCIM Provisioning.
- Generate or copy the SCIM token if a token is not already available.
- Copy the SCIM Base URL.
- Add the base URL and token to your identity provider.
- Add attribute mappings.
- Decide whether to sync groups.
- Save settings.
SCIM tokens are sensitive. Store the token in the identity provider or your approved secrets manager. If a token is exposed, rotate it.
Map attributes and groups
Map required identity attributes first:
| User data | Typical SCIM source |
|---|---|
userName or emails[type eq "work"].value | |
| First name | name.givenName |
| Last name | name.familyName |
| Display name | displayName |
Map organization custom fields only when the source system is truly the owner of that data.
Turn on group sync when your identity provider should create groups and manage membership. Make group and membership changes in the identity provider when it owns the group.
Verify success
SCIM is working when:
- The IdP accepts the SCIM Base URL and token.
- A pilot user is created or updated in Built LMS.
- Group membership appears as expected.
- Deactivation behavior matches your access policy.
- Synced profile fields match the source system.
Troubleshooting
Confirm SCIM is enabled, the token is current, the identity provider uses the correct SCIM Base URL, and provisioning is assigned to the expected users or groups.
Make group and membership changes in the identity provider when it owns the group.