Manage SCIM provisioning
SCIM provisioning lives at https://lengrowth.com/settings/scim.
When to use this
The page heading is SCIM Provisioning, and the subtitle says Manage provisioning tokens, sync status, and stale identity reconciliation.
The page has three practical sections:
SCIM Sync Status
SCIM Token Manager
SCIM API notes
At the top of the page are two actions:
Reload
Reconcile
Those actions let you refresh the current state or run a reconciliation pass when memberships drift out of sync.
Use the SCIM page when you want to:
Turn on token-based identity provisioning for a company
Create a fresh SCIM token
Copy the token into your identity tool
Revoke a token that should no longer work
Check whether the most recent sync succeeded
See how many memberships are managed or stale
Reconcile the identity state after a configuration change
If you are still setting up the identity provider itself, go to https://lengrowth.com/settings/sso first. SCIM sits on top of that setup.
Step-by-step
Select the company you want to manage.
Wait for the sync status and token list to load.
Confirm that the page is showing the correct workspace.
If no company is selected, LenGrowth will ask you to choose one before it can manage provisioning tokens.
The SCIM Sync Status card is the quickest way to understand the current state.
It can show:
Whether SCIM is enabled
The current sync status
The last sync time
The last sync error
How many memberships are managed
How many memberships are stale
Use this card before you make any token changes. If the status looks unhealthy, the sync error or stale membership count is the first clue to check.
The token manager lets you create provisioning tokens with a label.
Enter a token label, such as Production SCIM token.
Click the create action in the token manager.
Copy the token when LenGrowth shows it.
Store the token in your identity platform right away.
The page makes an important promise here: the token is only shown once. That means you should copy it immediately and keep it somewhere secure before you leave the page.
If you forget to copy it, the safest approach is to create a new token and revoke the old one if you are sure it will not be used.
Find the token you want to use.
Click the copy action.
Paste it into the SCIM configuration field in your identity system.
Confirm that the identity provider accepted it.
The page uses the clipboard directly, so the copy action is fast. Still, it is worth checking the token label before you copy so you do not paste the wrong value into your provisioning tool.
If a token should no longer be trusted, revoke it from the manager.
Find the token in the list.
Click the revoke action.
Confirm the revocation.
Check that the token status changes to revoked.
Use revocation when a token is exposed, retired, or replaced. Revoking old tokens is part of keeping the provisioning surface tidy.
The Reconcile button is for when membership state needs to be realigned.
Check the sync status card first.
Click Reconcile.
Wait for the success toast.
Review the updated membership counts after the page reloads.
The page uses reconciliation to reduce drift between managed memberships and what the workspace expects. If you recently changed SSO or provisioning settings, reconciliation is the next thing to try after the configuration is saved.
At the bottom of the page, the SCIM API notes card shows the endpoints your provisioning tool should know about.
The card lists:
/api/scim/v2/Users
/api/scim/v2/Groups
/api/scim/v2/ServiceProviderConfig
/api/scim/v2/Schemas
These notes are there so your identity provider or provisioning tool can connect to the right endpoint family. Keep them handy while you are wiring up the external system.
After you create a token, revoke a token, or run reconciliation, LenGrowth updates the provisioning state for the selected company.
You should expect:
The sync status card to refresh
The token list to show the current token state
The managed and stale membership counts to update when reconciliation completes
The provisioning token to be used by your identity system rather than by a user manually
SCIM is an administrative setup page. It does not change the everyday task experience directly, but it does affect how people enter and stay in the workspace.
Try reloading the page first, then check the sync status for a more specific error. If the error persists, revisit the SSO configuration and confirm SCIM is enabled there too.
That usually means you still need to turn on SCIM in the SSO settings page for the same company.
No tokens have been created yet. Create your first token from the token manager.
SCIM is always company-specific. Confirm the selected company in the header before you create or revoke anything.
Common problems
That is expected. The token is only shown once, so create a new token if needed and copy it immediately.
Related articles