---
title: "Manage SCIM"
canonical: "https://help.agiloft.com/space/HELP/779091993/Manage+SCIM"
format: markdown
---
This article includes information about common administrative tasks to help you manage your SCIM integration.

# Manage user records

When SCIM provisioning is enabled, your identity provider (IdP) serves as the source of truth for user accounts. The IdP sends user updates to Agiloft CLM according to its provisioning schedule, which may be near-real-time or at regular intervals. This is a one-way synchronization; changes in Agiloft CLM aren't sent to the IdP.

You can manually update user records in your KB as needed. However, changes to fields that are mapped to SCIM user attributes are overwritten the next time the IdP synchronizes the user. To determine which fields are managed by SCIM, review the user attribute mappings in the appropriate SCIM profile. To view user attribute mappings:

1. Go to **Setup > Access > Configure SCIM**.
2. Edit the SCIM profile and go to the User Attributes tab.
3. Review the Agiloft CLM fields selected under User Attribute Mapping. Click Show more to view the complete list.

Avoid making changes to any of the Agiloft CLM fields that are mapped to SCIM attributes.   

## User matching

In Agiloft CLM, incoming users are matched on the SCIM `userName` attribute. To ensure users are matched correctly, make sure the IdP sends a unique value for `userName` and that it matches the value in the Agiloft CLM field mapped to `userName` in the SCIM profile. By default, `userName` is mapped to the Login field.

## User activation and deactivation

In Agiloft CLM, users are activated and deactivated using the User is Active field in the People table and its subtables. When your IdP sends a SCIM request where the active attribute is true, Agiloft CLM sets User is Active to true and the user is activated. When the IdP sends a delete request or an update request where active is false, the system sets User is Active to false and the user is deactivated. For more information, see [Deactivate Users](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43717058).

# Manage SCIM profiles

A SCIM profile defines how Agiloft CLM receives and processes provisioning requests from an identity provider (IdP). Most organizations only need one SCIM profile. However, you can create multiple profiles to support different provisioning configurations, environments, or IdPs. For example, you might maintain separate profiles for testing and production, use different attribute mappings for different groups of users, or connect multiple IdPs to the same KB.

> 📝 If you set up multiple SCIM profiles, configure your IdP so that each user is provisioned through only one profile. If the same user is synchronized through multiple profiles, updates may overwrite values from another profile.

## Add a profile

To add a new SCIM profile, follow the instructions in [Set Up Agiloft CLM](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/778928159/Set+Up+SCIM#configure_kb).

## Disable a profile

You can disable a SCIM profile if you need to temporarily stop provisioning users without deleting the configuration. For example, you might disable a profile while troubleshooting or migrating to a different identity provider. You can re-enable the profile at any time.

To disable a profile:

1. Go to **Setup > Access > Configure SCIM**.
2. Select the checkbox next to the profile you want to disable and click Disable.

To enable a disabled profile, select the profile and click Enable. To remove a profile from the system, select the profile and click Delete.  

# Manage tokens

SCIM bearer tokens allow your identity provider to authenticate with the Agiloft CLM SCIM API and perform provisioning operations. Each SCIM profile can have multiple active tokens, making it possible to rotate credentials without downtime, maintain separate credentials for different clients or environments, and revoke tokens when a credential is no longer needed or suspected to be compromised. Allowing the use of multiple tokens helps improve security while minimizing disruption to user provisioning.

## > Macro (anchor)

Add a token

To add a token:

1. Go to **Setup > Access > Configure SCIM** and edit the profile you want to add a token to.
2. Go to the Bearer Tokens tab.
3. Under Bearer Tokens, click Generate Token.
4. Enter a unique label for the token and click Generate Token at the bottom of the screen.
5. Click Copy Token to copy the generated token, then save it in a secure location. Make sure you copy the token now because it can’t be displayed again.
6. Click Save to add the token to the profile. The token is Active by default.

You can now configure your identity provider to use that token in the SCIM endpoint connection.

## Revoke a token

To revoke or delete a token:

1. Go to **Setup > Access > Configure SCIM** and edit the profile for which you want to revoke or delete a token.
2. Go to the Bearer Tokens tab.
3. Under Bearer Tokens, select the token you want to revoke and click Revoke Token. Or you can click Delete to remove the token from the system. Revoking a token changes the status to Revoked.

You can’t reactivate a revoked token. If you need to add an active token to a profile, create a new one. See [Add a Token](#add_token).

#### Related articles

> Macro (contentbylabel)