Documentation › Organization settings
User provisioning (SCIM)
Let Microsoft Entra ID, Okta or OneLogin add, update and remove Embiro BI members automatically with SCIM 2.0.
SCIM (System for Cross-domain Identity Management) lets your identity provider manage Embiro BI members for you. When someone joins, they are added. When they change name or email, the change follows. When they leave and are disabled in your IdP, they lose access to Embiro BI at once.
Who can do this: the Super Admin. It is part of the "Single sign-on (SSO) + SCIM" plan feature. Set up single sign-on first.
1. Create a SCIM token
- Open Settings → Single sign-on → 4. User provisioning (SCIM), optional.
- Click Create token. Give it a name, such as Entra ID.
- Copy the token now. It starts with
scim_and is shown only once.
The section also shows the SCIM base URL (Tenant URL):
https://app.embirobi.com/scim/v2
You can have up to 5 active tokens. Revoke a token there when you no longer need it.
2. Configure your identity provider
- Microsoft Entra ID
- Enterprise applications → your Embiro BI app (or New application → Create your own) → Provisioning → mode Automatic. Tenant URL: the SCIM base URL. Secret Token: the token. Test Connection, then Save. Under Mappings, keep
userNamemapped to the user's email (map it tomailif your UPNs differ from email addresses). Assign the users or groups to provision, then Start provisioning. - Okta
- Your app → General → enable SCIM provisioning → Provisioning → SCIM connector base URL: the SCIM base URL; unique identifier field:
userName; supported actions: push new users, push profile updates; authentication mode HTTP Header with the token. Then enable Create Users, Update User Attributes and Deactivate Users under To App. - OneLogin and others
- Use the SCIM 2.0 base URL and the token as a bearer token, with
userName(the email) as the unique identifier.
What the IdP can do
| In your IdP | In Embiro BI |
|---|---|
| Assign a user | They join with the SSO default role, if a seat is free |
| Change their name or email | Updated |
| Unassign or disable them | Their membership ends and their seat is freed. Their account is turned off if they belong to no other organization |
| Re-enable them | They come back with the role they had, if a seat is free |
| Delete them | Same as disable, and the account is deleted if nothing needs it |
Only people with an email in your verified domains are managed this way. The Super Admin is never touched, and roles (Admin, Analyst, Business User) stay managed on Settings → Team Members. Groups aren't provisioned.
Each action is recorded in the Activity log as done by the identity provider.
Something unclear or missing? Tell us and we'll improve this page.