Documentation Index
Fetch the complete documentation index at: https://help.skillsdb.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
SCIM groups are how SkillsDB determines what a provisioned user can do. When a SCIM event arrives from your identity provider, SkillsDB looks at the user’s current group memberships and sets their SkillsDB permission level based on the highest-privilege group they belong to. There are two kinds of SCIM groups:- Default SCIM groups — two built-in groups (
SkillsdbGlobalAdminsandSkillsdbFullAccess) that administrators cannot delete. These grant Admin and Full Access respectively. - Custom SCIM groups — any other group provisioned from your identity provider. These are either auto-created when the first member is provisioned, or created manually by a SkillsDB administrator. Each custom group has a configurable permission level and can trigger automatic career assignment.
Prerequisites
Before managing SCIM groups, make sure you have:- Permission level: SkillsDB administrator
- Setup requirement: An active SCIM connection (see SCIM Setup)
- Access requirement: Settings > SSO & SCIM > Configure SSO and SCIM settings
Default SCIM groups
SkillsDB ships with two default SCIM groups. Create groups in your identity provider with exactly these names — any user added to one of them receives the corresponding SkillsDB permission level on the next sync.| Identity provider group name | SkillsDB permission level | What the user can do |
|---|---|---|
SkillsdbGlobalAdmins | Admin | Full system access, including configuration, libraries, and user management. |
SkillsdbFullAccess | Full Access | Access to all people, skills, training, and reports across the company. No configuration access. |
Custom SCIM groups
Any SCIM group you provision from your identity provider that is not one of the two default groups is treated as a custom SCIM group. Custom groups are useful when:- You want to grant Full Access or Admin through a group name that matches your organization’s naming conventions
- You want to assign careers automatically when users join a specific group (see SCIM Career Automations)
- You want to deactivate provisioning for a specific group without removing it from your identity provider
- Auto-created: When a user is provisioned with membership in a group that does not yet exist in SkillsDB, the group is auto-created with Basic permission and no career automations. An administrator can upgrade it later.
- Manually created: An administrator creates the group in SkillsDB before provisioning users into it. This is the right approach when you want to set the permission level and career automations before the first user arrives.
How permission levels resolve when a user belongs to multiple groups
A user’s effective SkillsDB permission level is the highest among their active SCIM group memberships, evaluated in this order:- If the user belongs to any active group with permission Admin, they receive Admin
- Otherwise, if the user belongs to any active group with permission Full Access, they receive Full Access
- Otherwise, the user receives Basic
- Basic users who have direct reports assigned to them are automatically promoted to Manager
How to create a custom SCIM group
Open the SSO & SCIM settings
Enter the group details
Select the permission level
Optionally add career automations
How to edit a custom SCIM group
Select the edit icon in the Action column of the Custom SCIM Groups table. The edit modal lets you change the description, permission level, and career automations. The group name is disabled in edit mode and cannot be changed. Permission-level changes apply to existing members on the next sync — SkillsDB recalculates each member’s effective permission level after the change.How to deactivate or reactivate a custom SCIM group
Select the archive icon in the Action column. Deactivated groups stop affecting SkillsDB users:- New SCIM events referencing a deactivated group are silently ignored
- Existing members keep their current permission level (derived from their other active groups)
- The group remains visible in the Custom SCIM Groups table with an
Inactivestatus badge
Manager role
The Manager role is not configured through SCIM groups. SkillsDB sets it automatically when SCIM events establish a reporting relationship:- When a SCIM event sets another user’s manager to a Basic user, the Basic user is automatically promoted to Manager
- Users who already hold Admin, Full Access, or Manager are not changed
- Managers have additional capabilities in SkillsDB, including access to team-specific pages and the ability to assign learning plans to their reports
Common Questions
Can I rename the default SCIM groups?
Can I rename the default SCIM groups?
SkillsdbGlobalAdmins and SkillsdbFullAccess are hardcoded in SkillsDB. Create identity-provider groups with these exact names to grant the corresponding permission levels. If you need different names, use custom SCIM groups instead.What happens to a user who is in both a custom Admin group and the default SkillsdbFullAccess group?
What happens to a user who is in both a custom Admin group and the default SkillsdbFullAccess group?
Do I need to create a custom SCIM group in SkillsDB before provisioning users into it?
Do I need to create a custom SCIM group in SkillsDB before provisioning users into it?
What's the difference between deactivating a custom group and deleting it from my identity provider?
What's the difference between deactivating a custom group and deleting it from my identity provider?
Why isn't a user I added to SkillsdbGlobalAdmins becoming an admin in SkillsDB?
Why isn't a user I added to SkillsdbGlobalAdmins becoming an admin in SkillsDB?
SkillsdbGlobalAdmins (case-sensitive).Can a user be in more than one custom SCIM group?
Can a user be in more than one custom SCIM group?