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.
First provisioning only (assign on first join only) or Always assign (assign on every sync).Overview
Career automations tie SCIM group membership to SkillsDB career assignments. When a user is provisioned into a custom SCIM group that has career automations attached, SkillsDB assigns the configured careers to that user automatically — no manual assignment required. Career automations are useful when:- New hires in a specific role should always start with a standardized career (for example, every new
FinanceAnalystsSCIM group member gets the “Finance Analyst” career) - You want careers to re-sync every time a user’s group membership changes, ensuring their assigned careers always match their current role
- You manage team membership in your identity provider and want SkillsDB career assignments to follow automatically
SkillsdbGlobalAdmins and SkillsdbFullAccess) do not support career automations.
Prerequisites
Before setting up career automations, make sure you have:- Permission level: SkillsDB administrator
- Setup requirement: At least one custom SCIM group (see SCIM Groups and Permissions)
- Setup requirement: The careers you want to assign already exist in SkillsDB
- Access requirement: Settings > SSO & SCIM > Configure SSO and SCIM settings
What a career automation contains
Each career automation on a custom SCIM group has three fields:| Field | Required | Purpose |
|---|---|---|
| Career | Yes | The SkillsDB career to assign to users in this group. |
| Level | No | The career level to assign. Populated dynamically from the selected career. If left blank, SkillsDB assigns the first available level. |
| Scope | Yes | Controls when the assignment runs. See How scope controls assignment timing below. |
How scope controls assignment timing
The Scope field is the most important knob on a career automation. It determines whether the automation runs only once per user, or every time the user is synced.| Scope | When the career is evaluated | Best for |
|---|---|---|
| First provisioning only | Only the first time the user becomes a member of this group. Once the automation has run for a user, subsequent syncs skip it. | Onboarding defaults. Use when you want to seed a career and let managers reassign it later without SkillsDB restoring it. |
| Always assign | Every time the user is synced to the group. If the career is no longer assigned, SkillsDB re-assigns it. If a target level is configured and the current level differs, SkillsDB updates the level. Otherwise no-op. | Enforcing a standardized career. Use when the SCIM group authoritatively defines what career the user should hold. |
How to add a career automation
Career automations are configured in the same modal used to create or edit a custom SCIM group. There is no separate screen.Open the SSO & SCIM settings
Open the group
Scroll to the Career Automations section
Add an automation
- Select a Career from the searchable dropdown
- Select a Level if the career has multiple levels (optional)
- Select a Scope: First provisioning only or Always assign
Add more automations or remove one
How to change or remove a career automation
To change an existing automation, edit the custom SCIM group and modify the automation row. Changes apply to future SCIM events — they do not retroactively re-run against current members unless those members are synced again. To remove an automation, select the trash icon next to its row and save. Careers that were previously assigned by the removed automation remain on the users’ profiles. Removing an automation does not un-assign careers from anyone — it only stops the automation from running in the future.What happens when a user is deactivated
When a SCIM-provisioned user is deactivated (removed from all SCIM groups, disabled in the IdP, or unassigned from the SCIM application), SkillsDB cleans up career automation records associated with that user’s SCIM group memberships. The user’s actual career assignments are preserved on their (now inactive) profile for historical and reporting purposes. If the same user is later reactivated through SCIM and re-provisioned into groups with career automations, the automations run as if they were a new user — First provisioning only automations will run again, treating the reactivation as a first provisioning.Common Questions
What happens if I set scope to Always assign and a manager removes or changes the career in SkillsDB?
What happens if I set scope to Always assign and a manager removes or changes the career in SkillsDB?
Can I add career automations to the default SkillsdbGlobalAdmins or SkillsdbFullAccess groups?
Can I add career automations to the default SkillsdbGlobalAdmins or SkillsdbFullAccess groups?
FinanceAdmins), set its permission level to Admin or Full Access, and attach a career automation.Will changing an automation's career retroactively update existing group members?
Will changing an automation's career retroactively update existing group members?
How do I verify a career automation ran for a specific user?
How do I verify a career automation ran for a specific user?
What if the career I want to automate doesn't exist yet in SkillsDB?
What if the career I want to automate doesn't exist yet in SkillsDB?
Can I have multiple automations that assign the same career?
Can I have multiple automations that assign the same career?