For AI agents and LLMs: a machine-readable index is available at llms.txt. A plain-Markdown version of any documentation page is available by appending .md to its URL.
Skip to main content

SCIM Provisioning: Users & Groups

TestMu AI supports SCIM 2.0 (System for Cross-domain Identity Management) for user and group provisioning. After you connect your identity provider (IDP), the users and groups you manage there are created, updated, and deactivated in your TestMu AI organization automatically.

Supported Features​

FeatureDescription
User provisioningCreate, update, and deactivate user accounts from your IDP. See User Provisioning
Group provisioningSync IDP groups and map each group to teams, a concurrency group, or a sub-organization, manually or with rules. See Group Provisioning
Organization rolesSet each user's organization role (Admin, User, or Guest) from your IDP. See Role Assignment
Custom rolesAssign custom roles to the teams a rule creates and to new SCIM users. Available only if your organization has Custom Roles & Permissions (RBAC) enabled. See Custom Roles with SCIM

Prerequisites​

  • An Enterprise plan
  • Single sign-on (SSO) configured for your organization
  • Admin access to your TestMu AI organization
  • An identity provider that supports SCIM 2.0
  • (Optional) Custom Roles & Permissions (RBAC) enabled, only if you want SCIM to assign custom roles

Group provisioning has additional requirements. See Before You Start.

Supported Identity Providers​

TestMu AI works with any identity provider that supports SCIM 2.0. Step-by-step guides are available for:

For any other identity provider, follow Setup.

How Provisioning Works​

Once SCIM is set up, you manage access in your IDP and TestMu AI stays in sync. Users sign in with SSO and do not need an invitation.

When youTestMu AI
Assign a user to the TestMu AI appCreates the account in your organization with an organization role. With custom roles: the user also gets the default roles, if they are turned on
Add the user to a group that is pushed to TestMu AIAdds the user to the teams, concurrency group, or sub-organization the group is mapped to. With custom roles: the user also gets the custom roles of each team
Move the user between groups, or change a group's rolesUpdates the user's teams and roles on the next sync. See What Happens When...
Unassign or deactivate the userDeactivates the account and frees the license seat. The account is not deleted. With custom roles: default custom roles are removed
Custom roles need RBAC

Custom roles are part of Custom Roles & Permissions (RBAC), which is not enabled for every organization. Without it, SCIM still provisions users and groups, sets organization roles (Admin, User, Guest), and maps groups to teams, concurrency groups, and sub-organizations. The role options described on this page (Roles in the team on a rule, the Roles column on the Rules tab, and Auto-assign roles to new SCIM users) are shown only when Custom Roles & Permissions is enabled.


Setup​

Complete the prerequisites before you start.

Step 1: Copy SCIM Credentials​

Go to Settings > Organization Settings > Security > SCIM Provisioning. Copy the SCIM Base URL and Bearer Token.

SCIM Base URL and Bearer Token

Step 2: Configure Your IDP​

Paste the SCIM Base URL and Bearer Token into your IDP's provisioning settings.

Full walkthrough: Okta SCIM Guide

  1. Applications > your TestMu AI app > Provisioning tab > Configure API Integration
  2. Check Enable API Integration, paste credentials, click Test API Credentials > Save
  3. Under To App, enable: Create Users, Update User Attributes, Deactivate Users
  4. Assignments tab > assign users or groups
  5. (For groups) Push Groups tab > Push Groups > Find by name or rule
tip

Member changes in pushed Okta groups are automatically synced to TestMu AI.



User Provisioning​

How It Works​

ScenarioWhat happens
New user (email doesn't exist)Account created and added to your org. With Custom Roles & Permissions enabled, the user also gets any default SCIM roles you have turned on
Existing user (same org)Attributes (role, active) updated
Existing user (different org)Not provisioned (400 Bad Request). Invite the user to your organization first, then SCIM can manage them
User deactivated (active: false or DELETE)Account deactivated, license seat freed, default SCIM roles removed. The account is not deleted
User reactivated (active: true)Account reactivated. Default SCIM roles granted again

Schema & Attributes​

{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:User",
"urn:ietf:params:scim:schemas:extension:LambdaTest:2.0:User"
],
"userName": "jane@company.com",
"active": true,
"name": { "givenName": "Jane", "familyName": "Doe", "formatted": "Jane Doe" },
"urn:ietf:params:scim:schemas:extension:LambdaTest:2.0:User": {
"OrganizationRole": "User",
"LambdatestGroup": "Engineering"
}
}

Standard Attributes

AttributeRequiredNotes
userNameYesMust be a valid email. Cannot be changed after creation.
activeYestrue = enabled, false = deactivated
nameYesgivenName, familyName, formatted

Custom Attributes (TestMu AI Extension)

These attributes are part of the urn:ietf:params:scim:schemas:extension:LambdaTest:2.0:User extension schema. To send them from your IDP, add this schema URN to your IDP's custom attribute configuration.

AttributeRequiredValuesNotes
OrganizationRoleNoAdmin, User, GuestSets the user's organization role. Defaults to User if not provided.
LambdatestGroupNo(concurrency group name)Assigns the user to a concurrency group by name. The group must already exist. Contact support to enable concurrency groups.

For PATCH operations, use the fully qualified SCIM path:

  • OrganizationRole: urn:ietf:params:scim:schemas:extension:LambdaTest:2.0:User:OrganizationRole
  • LambdatestGroup: urn:ietf:params:scim:schemas:extension:LambdaTest:2.0:User:LambdatestGroup

What can be updated: OrganizationRole, LambdatestGroup, and active can be updated via SCIM. userName is immutable after creation. name can only be changed from TestMu AI Account Settings.

User API Operations​

Request: POST https://auth.lambdatest.com/api/scim/Users

{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:User",
"urn:ietf:params:scim:schemas:extension:LambdaTest:2.0:User"
],
"userName": "jane@company.com",
"active": true,
"name": { "givenName": "Jane", "familyName": "Doe", "formatted": "Jane Doe" },
"urn:ietf:params:scim:schemas:extension:LambdaTest:2.0:User": {
"OrganizationRole": "User",
"LambdatestGroup": "Engineering"
}
}

Response: 201 Created

{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:User",
"urn:ietf:params:scim:schemas:extension:LambdaTest:2.0:User"
],
"id": "23123",
"userName": "jane@company.com",
"active": true,
"name": { "givenName": "Jane", "familyName": "Doe", "formatted": "Jane Doe" },
"urn:ietf:params:scim:schemas:extension:LambdaTest:2.0:User": {
"OrganizationRole": "User",
"LambdatestGroup": "Engineering"
}
}


Group Provisioning​

Group provisioning syncs groups from your IDP and maps each group to teams, a concurrency group, or a sub-organization in TestMu AI. Membership changes in your IDP are applied to the mapped entities automatically.

Setting up group provisioning takes five steps:

  1. Turn on group provisioning.
  2. Create rules that map new groups by name to a team, a concurrency group, or both.
  3. Push groups from your IDP and review them on the Groups tab.
  4. Map or approve manually any group that a rule did not approve automatically.
  5. Change a group's mappings later, if needed.

How It Works​

TestMu AI stores a group and its members as soon as your IDP pushes them, even before the group is mapped. The mapping determines which teams, concurrency group, or sub-organization the members are assigned to.

Step 1: Your IDP (automatic)
Groups & members pushed via SCIM
↓
Step 2: TestMu AI (automatic)
Group stored & roles applied to members
Organization roles apply to members immediately, even without mapping
↓
Step 3: Admin (manual) or Mapping Rules (automatic)
Group mapped to teams, a concurrency group, or a sub-organization (plus custom roles for teams)
↙
↓
↘
Team
Additive
Multiple teams allowed
Concurrency Group
Exclusive
User can only belong to one
Sub-Organization
Exclusive
User can only belong to one

Before You Start​

You needWhere to check
User provisioning working, so the group's members exist in TestMu AIYour IDP's provisioning logs
Group provisioning activated for your organizationThe Enable SCIM Group Provisioning toggle is visible on the SCIM Provisioning page
Teams enabled, and Concurrency Groups or Sub-Organizations if you want to map to themYou only see the options your organization has. Missing one? Ask support to enable it
(Optional) Custom roles created, if teams should get roles automaticallySettings > Organization Settings > Members > Custom Roles & Permissions
note

Group provisioning, Teams, Concurrency Groups, and Sub-Organizations are not enabled by default. Reach out to our 24/7 chat support or email support@testmuai.com to get them activated for your organization.

Step 1: Turn On Group Provisioning​

  1. Go to Settings > Organization Settings > Security > SCIM Provisioning
  2. Turn on Enable SCIM Group Provisioning

The page now shows three tabs:

TabWhat you do there
GroupsSee every group your IDP has synced, and choose the teams its members join
RulesMap new groups automatically by name. With Custom Roles & Permissions enabled, a rule can also assign roles to the team
SettingsBase URL, Bearer Token, and the group provisioning toggle. With Custom Roles & Permissions enabled, also the default roles for new users
SCIM Provisioning page on the Settings tab with the Base URL, Bearer Token, Enable SCIM Group Provisioning toggle and Auto-assign roles to new SCIM users toggle with one role selected

The screenshots on this page are from an organization with Custom Roles & Permissions enabled. Without it, the role fields are not shown.

When toggled OFF: New IDP group operations (create/update/delete) are rejected with 403. Existing groups, mappings, and assignments are preserved. Nothing is deleted. Toggle back ON to resume syncing.

Step 2: Create Rules​

A rule maps new IDP groups automatically, based on the group name. Create rules before your IDP pushes the groups, because a rule applies only to groups that sync after the rule exists.

One rule can create a team and a concurrency group together, both named after the IDP group. With Custom Roles & Permissions enabled, the rule can also assign roles to the team.

To create a rule:

  1. Open the Rules tab and click Add rule
  2. Under When the group name, choose a match type and enter the pattern. See Match types
  3. Under Map to, select Team, Concurrency group, or both. Sub-organization can only be selected on its own
  4. (Optional. Shown only when Team is selected and Custom Roles & Permissions is enabled) Under Roles in the team, select one or more roles. Every team this rule creates gets these roles. See Custom Roles with SCIM
  5. Turn on Approve automatically to map matching groups without admin review
  6. Click Add rule
Add rule dialog: when the group name starts with a prefix, Team and Concurrency group both selected, one role in the team, and Approve automatically on

Match types​

Matches group names that start with the text you enter (case-insensitive). Enter plain text without a wildcard: a trailing * is treated as a literal character.

eng- matches eng-backend, eng-frontend, ENG-DevOps

What a rule creates​

Map toResult when Approve automatically is on
TeamCreates a team named after the group (or reuses a team with that name) and adds the members
Concurrency groupCreates a concurrency group named after the group (or reuses it) and moves the members into it. A newly created concurrency group starts with no concurrency allocated, so set it under Members > Groups
Team + Concurrency groupDoes both of the above for the same group
Sub-organizationMaps the group to an existing sub-organization with the same name. Sub-organizations are never created automatically, and this option can't be combined with the other two

When Approve automatically is off, nothing is created. The group stays in Needs approval until an admin approves it.

Rule order​

Rules are evaluated from the top of the list. The first matching rule applies, and the rules below it are skipped. If no rule matches, the group stays Not mapped until an admin maps it manually.

Rules tab listing three rules: a prefix mapped to Team + Concurrency group, a prefix mapped to Team, and a catch-all that needs approval

Place specific rules at the top and an is any group catch-all rule at the bottom. Click Change order to move rules up or down.

Reorder Rules dialog with up and down arrows next to each rule
Rules apply to new groups only

A new, edited, or deleted rule affects only groups that sync after the change. Groups that are already mapped keep their teams, concurrency groups, and roles. To change those, change the group.

Step 3: Push Groups and Review Them​

Push or assign your groups in your IDP (see the guides for Okta, Microsoft Entra ID, JumpCloud, and PingOne). Each group appears on the Groups tab within a few seconds of the push.

Groups tab listing synced IDP groups with their status, teams, concurrency group and last synced time
StatusWhat it meansWhat to do
ApprovedThe group is mapped and its members are syncedNo action needed
Needs approvalA rule matched the group, but an admin has to approve it before members are addedApprove it
Not mappedNo rule matched and no mapping is selected. Members are not assigned to any entityMap it manually
Target deletedA mapped team, concurrency group, or sub-organization was deletedSee Deleted Target

The yellow banner in the example above appears only when a user is in two groups that can't share members. See Conflicts.

Click a group to view its details. Entries that a rule created are marked Added by a rule. If the rule assigns roles, they are listed next to the team.

Group details on the Mappings tab: a team added by a rule with its rule roles, and a concurrency group added by a rule
  • Mappings tab: the teams, concurrency group, or sub-organization the group maps to.
  • Roles tab: roles your IDP sends for the group, and roles a rule added.
  • Members tab: who is in the group.

The teams also appear under Members > Teams with their custom roles, if any, and the concurrency groups under Members > Groups.

Teams list showing SCIM-provisioned teams, each with its custom role in the Custom Roles column

Step 4: Map or Approve a Group Manually​

Use this step for groups with the status Not mapped or Needs approval, or if you do not use rules.

  1. On the Groups tab, click the group. Its details open on the Mappings tab
  2. Under Teams, select one or more teams. Select a Concurrency group as well, if needed. Teams and concurrency groups must already exist, so create them first if required
  3. Click Save. The group is approved and members are updated in a few seconds
Group details for a group that needs approval, with a banner asking the admin to pick teams and save

If the group already lists its entries and shows Waiting for your approval., click Approve there, or use Approve in the group's ⋯ menu on the Groups tab.

What one group can map to

FieldHow manyWhat happens
TeamsAs many as you needMembers join every team listed
Concurrency groupOneMembers move to this concurrency group
Sub-organizationOneMembers move to this sub-organization. It can't be combined with teams or a concurrency group

Select an entity type for details:

Teams are additive: a user can belong to multiple teams at once, so there are no conflicts.

Auto-createYes, by a rule with Approve automatically on. A manual mapping needs an existing team
On member removalRemoved from team (unless another SCIM group also maps them there)
On group renameA team that a rule created is renamed to match the IDP group name, unless another SCIM group also maps to it. Teams you selected manually keep their names
ConflictsNone, teams are never exclusive

Team is the simplest mapping and the recommended starting point.

note

A team you add manually does not get a rule's roles. Grant custom roles to that team directly or send them from your IDP. See Custom Roles with SCIM.

Step 5: Change a Group's Mappings​

A rule sets a group's initial mappings. You can change the mappings of any group afterwards: open the group, edit the Mappings tab, and click Save.

Group details on the Mappings tab after a second team was added manually next to the team and concurrency group the rule created
ToDo this on the Mappings tabResult
Add the members to more teamsAdd the teamsMembers join every team listed. Entries the rule created stay
Use a different concurrency groupRemove the current one and pick anotherMembers move to the one you picked
Stop using a teamRemove the teamMembers leave that team, unless another SCIM group still maps to it. If a rule created it, the rule's roles are removed from the team
Share one team between several groupsAdd the same team on each groupA user stays in the team as long as one of their groups maps to it

Rules do not overwrite changes you save here. Rules run only when a group is first pushed or renamed in your IDP.

Map Several Groups to One Team​

More than one SCIM group can map to the same team. A user stays in the team as long as at least one of their SCIM groups maps to it, and leaves it when the last one stops.

Role Assignment​

This section covers organization roles (Admin / User / Guest). For custom RBAC roles, see Custom Roles with SCIM.

Organization roles can be set per-user (User extension OrganizationRole) or per-group (Group extension LambdatestRoles). They work independently of mappings: even unmapped groups apply their organization roles to members immediately.

When a user is in multiple groups with different roles, the highest-priority role wins: Admin > User > Guest

GroupRole
eng-teamUser
org-adminsAdmin
Effective roleAdmin (highest wins)

Roles can be upgraded and downgraded. The effective role is always the highest across all current group memberships. Removing a user from one group only downgrades their role if no other group provides it.

ScenarioWhat happens
User added to a group with Admin roleRole upgraded to Admin (if currently lower)
User removed from the Admin groupRole recomputed, drops to next highest (e.g., User) if no other group gives Admin
All groups removed, or no roles setRole defaults to User
Group's LambdatestRoles changed from Admin to GuestAll members' roles recomputed, may downgrade

Custom Roles with SCIM​

This section applies only to organizations with Custom Roles & Permissions (RBAC) enabled. If your organization does not use it, skip this section.

The roles above are organization roles (Admin / User / Guest). With Custom Roles & Permissions, SCIM can also grant custom roles automatically, so users have the right access as soon as they are provisioned.

Prerequisites

Custom roles through SCIM need Custom Roles & Permissions enabled for your organization, and SCIM Group Provisioning enabled for team-based roles. Create the custom roles first under Settings > Organization Settings > Members > Custom Roles & Permissions. Reach out to our 24/7 chat support if you don't see these options.

There are three ways to grant custom roles with SCIM. Use any one of them, or combine them:

MethodConfigured inWho gets the roleBest for
Roles in the team on a ruleTestMu AI (Rules tab)Every team the rule creates, and so every member of those teamsGroups that follow a naming convention, with no role setup in your IDP
Custom role names in LambdatestRolesYour IDP (group extension attribute)The team the group is mapped toKeeping all role assignment in your IDP
Auto-assign roles to new SCIM usersTestMu AI (Settings tab of the SCIM Provisioning page)Each user provisioned after you turn it onA baseline role every new user should start with
SCIM Provisioning page on the Settings tab with the Base URL, Bearer Token, Enable SCIM Group Provisioning toggle and Auto-assign roles to new SCIM users toggle with one role selected

Pick Roles in the team on a rule that maps to Team. When a group matches the rule, TestMu AI creates (or reuses) the team, attaches those roles to it, and adds the group's members. Everyone in the team inherits the roles.

Example: your IDP groups follow the convention acme-qe-web-<squad> and acme-qe-mobile-<squad>.

OrderWhen group nameMaps toRolesApproval
1Starts with acme-qe-web-TeamQE-Web-TesterAutomatic
2Starts with acme-qe-mobile-TeamQE-Mobile-TesterAutomatic

When your IDP pushes acme-qe-web-payments, the team acme-qe-web-payments is created with the QE-Web-Tester role and its members are added. No manual role assignment is needed. The Custom Roles column under Members > Teams shows the result.

Roles in the team picker listing the default Admin, User and Guest roles and the organization's custom roles, with one custom role selected
Teams list showing SCIM-provisioned teams, each with its custom role in the Custom Roles column
  • The Roles in the team field appears only when Team is selected and Custom Roles & Permissions is enabled.
  • You can select more than one role. Default roles (Admin, User, Guest) and your custom roles appear in one searchable list.
  • With Approve automatically OFF, the group waits as Needs approval. The roles are attached when an admin approves it.
  • The roles go to the team the rule creates. Teams you add to the group manually do not get them.
  • If a mapped role is deleted later, the rule shows a warning. Edit the rule and reselect a role.

How the sources work together

  • All sources add up. A team can hold roles from a rule and from your IDP at the same time. A user gets the roles of every team they belong to, plus any default roles.
  • Each source removes only what it granted. Removing a role from a rule's team never strips the same role your IDP granted, and the other way round.
  • Rules are forward-only. Editing or deleting a rule doesn't change roles on teams it already created. To change access for existing teams, edit the custom role itself under Custom Roles & Permissions. That change applies to everyone who holds the role.

What happens to rule roles when things change

ChangeResult
User added to the IDP groupJoins every team the group maps to and inherits their roles
User removed from the IDP groupLeaves those teams (unless another of their SCIM groups maps to the same team) and loses the roles that came from them
Group renamed, still matches the same ruleThe team the rule created is renamed to match. Roles kept
Group renamed to match a different ruleOld rule's roles removed. The group returns to Needs approval under the new rule. Teams added manually are not affected
Group renamed so no rule matchesRule's roles removed from the team. The group returns to Needs approval. Teams added manually are not affected
Group deleted in your IDPMembers leave the mapped teams. Rule's roles removed from the team
Admin removes the rule's team from the group's Mappings tabMembers leave the team (unless another SCIM group maps to it). Rule's roles removed from the team
Rule edited or deletedNo change to existing teams. Applies to new groups only

Conflicts​

Teams don't have conflicts

If you map groups only to Teams, you can skip this section. A user can belong to several teams, so teams never conflict.

A conflict occurs when a user belongs to several SCIM groups whose mappings cannot apply to the same user at once. The user keeps their current assignment until an admin resolves the conflict. Nothing changes automatically.

When do conflicts happen?

When the same user is in two SCIM groups mapped to different concurrency groups. Example: Group A → "QA Pool" and Group B → "Dev Pool". The user can only be in one.


To resolve:

  1. Go to Settings > Organization Settings > Security > SCIM Provisioning and open the Groups tab. When conflicts exist, a banner shows how many users are in more than one group that can't share members
  2. Click Resolve. The Pending tab lists open conflicts and Resolved lists past decisions
  3. Each conflict card shows the Current group (where the user is now) and the Incoming group (the one trying to claim the user)
  4. Click Keep Current or Use Incoming
  5. TestMu AI remembers this decision. The same combination won't create a new conflict
Conflict Resolution panel showing one user with a current and an incoming group, and Keep Current and Use Incoming buttons
To avoid conflicts

Prefer teams when users need to be in multiple groups. Teams never create conflicts. Only use concurrency groups and sub-organizations when you need exclusive assignment.

Deleted Target​

If an admin deletes a team, concurrency group, or sub-organization that has an active SCIM mapping, the group's status changes to Target deleted.

Manual re-mapping required

When a target is deleted, TestMu AI does not create a replacement automatically, even if a matching rule has Approve automatically on. An admin must update the mapping to point to a new or recreated target.

To fix a group with a deleted target:

  1. Go to Settings > Organization Settings > Security > SCIM Provisioning and open the Groups tab
  2. Open the group with the Target deleted status. The deleted entry is no longer listed on its Mappings tab
  3. Pick a replacement (create it first if needed), or leave it out
  4. Click Save. Members are synced to what is listed

Group Schema & Attributes​

{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:Group",
"urn:ietf:params:scim:schemas:extension:LambdaTest:2.0:Group"
],
"displayName": "eng-backend",
"members": [{ "value": "12345" }, { "value": "67890" }],
"urn:ietf:params:scim:schemas:extension:LambdaTest:2.0:Group": {
"LambdatestRoles": ["User"]
}
}

Standard Attributes

AttributeRequiredNotes
displayNameYesMust be unique within your org
membersNoArray of { "value": "<user_scim_id>" }

Custom Attributes (TestMu AI Extension)

These attributes are part of the urn:ietf:params:scim:schemas:extension:LambdaTest:2.0:Group extension schema. To send them from your IDP, add this schema URN to your IDP's custom attribute configuration.

AttributeRequiredValuesNotes
LambdatestRolesNoAdmin, User, Guest, or custom role namesAdmin / User / Guest set the organization role of all members. Highest role wins if a user is in multiple groups. Custom role names are granted to the group's mapped team.

For PATCH operations, use the fully qualified SCIM path:

  • LambdatestRoles: urn:ietf:params:scim:schemas:extension:LambdaTest:2.0:Group:LambdatestRoles

Group API Operations​

Request: POST https://auth.lambdatest.com/api/scim/Groups

{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:Group",
"urn:ietf:params:scim:schemas:extension:LambdaTest:2.0:Group"
],
"displayName": "eng-backend",
"members": [
{ "value": "23123" },
{ "value": "23456" }
],
"urn:ietf:params:scim:schemas:extension:LambdaTest:2.0:Group": {
"LambdatestRoles": ["User"]
}
}

Response: 201 Created

{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:Group",
"urn:ietf:params:scim:schemas:extension:LambdaTest:2.0:Group"
],
"id": "50001",
"displayName": "eng-backend",
"members": [
{ "value": "23123", "display": "jane@company.com" },
{ "value": "23456", "display": "bob@company.com" }
],
"urn:ietf:params:scim:schemas:extension:LambdaTest:2.0:Group": {
"LambdatestRoles": ["User"]
},
"meta": {
"resourceType": "Group",
"created": "2025-01-15T10:30:00Z",
"lastModified": "2025-01-15T10:30:00Z"
}
}


What Happens When...​

This section lists what TestMu AI does when something changes in your IDP or in TestMu AI. No action is needed unless the last column says so.

You do this in your IDPWhat happens in TestMu AIAction needed?
Rename a groupGroup name updated. A team or concurrency group that a rule created is renamed to match. Rules re-evaluated. If the group now matches a different rule or no rule, rule roles are removed and the group returns to Needs approval. Teams added manually are not affected.Only if the group returned to Needs approval
Delete a groupGroup deleted. Members unassigned from its mapped entities. Roles recomputed. Conflicts resolved automatically.No
Add a member to a groupAdded to all mapped entities. Role recomputed.Only if a conflict is created
Remove a member from a groupUnassigned from mapped entities (only if no other group maps them there). Role recomputed.No
Re-push a previously deleted groupGroup restored. Members must be re-pushed. Mapping rules re-evaluated.Depends on rules
Change roles on a groupAll members' roles recomputed immediately. Custom role names are updated on the group's mapped team.No
Deactivate a userAccount deactivated. License seat freed. Default SCIM roles removed.No
Reactivate a userAccount reactivated. Default SCIM roles granted again.No


Troubleshooting​

API Errors​

ErrorCauseFix
401 UnauthorizedInvalid or expired Bearer TokenRegenerate in Organization Settings > Security
403 ForbiddenGroup Provisioning is disabledTurn on Enable SCIM Group Provisioning. See Enabling & Disabling
404 Not FoundID doesn't exist or belongs to a different orgVerify via a List call
409 ConflictGroup with same displayName already existsRename or delete the existing group
400 Bad RequestUser exists in a different organizationInvite them via team invite first

Common Issues​

IssueSolution
Members not appearing in teams or sub-organizationsThe group is Not mapped or Needs approval. Map or approve it from the Groups tab, or create a rule with Approve automatically on.
Members are in the SCIM group but not in the sub-organizationCheck for conflicts. The user may belong to another group with a competing exclusive mapping.
User has an unexpected roleCheck all SCIM group memberships. Roles follow highest-wins (Admin > User > Guest). The user may inherit Admin from another group.
User keeps getting re-added after manual removalSCIM is the source of truth. Remove the user in your IDP instead.
Group went back to Needs approval, or shows Target deletedThe group was renamed (rules re-evaluated) or a mapped entity was deleted. If renamed, open the group and approve it. If deleted, pick a new target.
Tests don't run in parallel for a team a rule set upA concurrency group that a rule creates starts with no concurrency allocated. Set it under Members > Groups.
Auto-approve didn't create my sub-organizationSub-organizations are never created automatically, because they have billing and setup requirements. Create the sub-organization first, then approve the group manually.
Roles in the team field is missing on a ruleSelect Team under Map to, and make sure Custom Roles & Permissions is enabled for your organization.
A rule with eng-* matches nothingStarts with takes plain text. Remove the *.
Can't pick a sub-organization on a groupA sub-organization can't be combined with teams or a concurrency group. Remove those first.
A SCIM team has no custom roleCheck that the group is Approved. Rules are forward-only, so a team created before the rule got its roles keeps its previous roles. Teams added to a group manually do not get rule roles.
A custom role from LambdatestRoles isn't appliedThe name must match a custom role exactly, and the group must be mapped to an approved team.
New users don't get the default roleCheck that Auto-assign roles to new SCIM users is ON with a role selected. Users provisioned before it was turned on are not updated.

FAQ​

QuestionAnswer
Can one rule create a team and a concurrency group?Yes. Select both Team and Concurrency group under Map to. Each matching group gets a team and a concurrency group named after it. See Create Rules.
Can a group be mapped to multiple targets?Yes. A SCIM group can map to several teams and one concurrency group at the same time. A sub-organization mapping stands alone. See Mapping Groups.
Can two SCIM groups map to the same team?Yes. A user stays in the team as long as one of their SCIM groups maps to it.
Can I disable group provisioning without losing data?Yes. The toggle only blocks new IDP operations. Existing groups, mappings, and assignments are preserved. Toggle back ON to resume.
Can I restore a deleted group?Yes. Push a group with the same displayName from your IDP. The group is restored. Members need to be re-pushed.
Can roles be downgraded?Yes. Roles are recomputed across all groups. If the highest role is removed, the effective role drops to the next highest. Defaults to User if none set.
What happens to a conflict when one group is deleted?The conflict is auto-resolved in favor of the remaining group. No admin action needed.
Does it matter whether a rule or an admin approved a group?No. Members are synced the same way, and both show as Approved.
Do rules overwrite existing mappings?No. Rules only apply when a group is first created or renamed. Mappings you set manually are not overwritten.
Does changing a rule's roles update existing teams?No. Rule changes are forward-only. To change access for existing teams, edit the custom role itself.
Do rule roles replace roles sent by my IDP?No. Both apply to the team, and removing one never removes the same role granted by the other.
Can I give every new user a starting role without group rules?Yes. Turn on Auto-assign roles to new SCIM users and select the roles.
Can rule roles be used with Concurrency group or Sub-organization targets?No. Rule roles apply to Team targets only.

That's all you need to know about SCIM Provisioning with TestMu AI. In case you have any questions please feel free to reach out to us via the 24/7 chat support or email us over support@testmuai.com.

Terminal First Testing With Kane CLI

Natural language browser & mobile app tests right from terminal.

×
Schedule Your Personal Demo
Kane CLI terminal

Help and Support

Related Articles