locale; this page uses it as the worked example.Overview
A custom SCIM attribute mapping lets a career automation read a value that your identity provider knows but SkillsDB has no field for. Today a career automation uses such a value for one purpose: the career’s initiation date, the date a person started in that career. The initiation date anchors training timelines and the “Started” date shown on the career. Without a mapping, a career automation assigns its career with an empty initiation date. SkillsDB receives SCIM events through Stytch, which passes through the standard SCIM user attributes but not identity-provider-specific properties such as Entra’semployeeHireDate. To bridge that gap, SkillsDB stores eleven standard SCIM attributes that have no field of their own in SkillsDB: locale, nickName, userType, timezone, preferredLanguage, profileUrl, name.middleName, name.honorificPrefix, name.honorificSuffix, costCenter, and organization. These are the spare attributes. They are never shown on the person’s profile. They exist only so that a career automation can read one of them.
A custom mapping therefore has two halves:
- In your identity provider, a mapping that writes the source value into one of the eleven spare attributes. The source can be any date your directory holds: a hire date, a role start date, a contract start date, or a custom extension attribute your HR system fills in.
- In SkillsDB, the Use custom mapping for career initiation date setting on a career automation, pointing at the same spare attribute.
Prerequisites
Before you begin, make sure you have:- Permission level: Microsoft Entra administrator access to the SkillsDB enterprise application, and SkillsDB administrator access
- Setup requirement: An active SCIM connection between Entra and SkillsDB (see SCIM Setup)
- Setup requirement: At least one custom SCIM group with a career automation (see SCIM Career Automations)
- Setup requirement: The source value filled in on the Entra users you want to cover, for example the Employee hire date property
How to choose the spare attribute
Pick one of the eleven spare attributes for each value you want to carry. Two rules decide the choice:- Nothing else in your Entra provisioning configuration maps to it. If the default Entra configuration already maps a directory property to the attribute, your value would fight with it.
localeis the recommended first choice because the default Entra provisioning configuration leaves it unmapped.nickName,userType,timezone,preferredLanguageandprofileUrlare usually unmapped as well. - One value per attribute. If you need two values, for example two different start dates for two automations, use two different spare attributes.
How to add the mapping in Entra
Add one attribute mapping to the provisioning configuration of the SkillsDB enterprise application. The example maps the Employee hire date property tolocale; substitute your own source and target.
Open the attribute mappings
Add the mapping
Save
employeeHireDate, one of the fifteen extensionAttribute properties synchronized from on-premises Active Directory, or a directory extension your HR integration writes. The value must reach SkillsDB as an ISO 8601 date (see What date formats SkillsDB accepts). A Direct mapping of employeeHireDate already produces that form. For a source stored in another format, use the Expression mapping type and Entra’s date formatting functions to output yyyy-MM-dd, then confirm the result on one user with Provision on demand before rolling it out.
How to turn on the mapping in SkillsDB
The mapping is a setting on each career automation. Turn it on for every automation whose career should receive the date.Open the SSO & SCIM settings
Edit the group
Turn on the custom mapping
locale.Save
What happens for newly provisioned users
When both halves of the mapping are in place, no further action is needed for new users. When Entra provisions a user into a group with a career automation, SkillsDB assigns the career and sets its initiation date from the mapped attribute in the same step. The SCIM event log records a Career Assigned event whose description ends with the date and the attribute it came from, for example “initiation date 2024-03-15 from SCIM attribute “Locale"". If the mapped value arrives in a later SCIM event than the one that assigned the career, SkillsDB fills the initiation date in when that later event arrives and records an Initiation Date Set event. If the mapped value is empty or is not a valid date, SkillsDB assigns the career without an initiation date. The Career Assigned event description then ends with “no valid initiation date in SCIM attribute “Locale"" (with the attribute you chose). The assignment itself is never blocked by a missing or invalid date.How to populate users who are already provisioned
Users provisioned before the Entra mapping existed have no mapped value stored in SkillsDB. Entra has to send their attributes again. There are two ways to trigger that.Test with one user first
Provision one user on demand
Check the event log
Check the career
Resend every user
Restart provisioning
Wait for the cycle to complete
Verify in the event log
Which careers are populated
As each resent user reaches SkillsDB, the stored value is applied to that user’s careers under these rules:What date formats SkillsDB accepts
The mapped value is read as a career initiation date only when it is an ISO 8601 date:2024-02-30 is rejected). Any other value, including day-first or month-first formats such as 15/03/2024, a real locale code such as en-US, or free text, is ignored: the career is assigned without an initiation date and the event log says so. A Direct Entra mapping of employeeHireDate produces an accepted form.
Common Questions
Which spare attribute should I use?
Which spare attribute should I use?
locale unless something else in your Entra provisioning configuration already maps to it. The default Entra configuration leaves locale unmapped, and SkillsDB does not read it for anything except this mapping. If locale is taken, any of the other ten attributes listed under How to choose the spare attribute works the same way. Use the same attribute in the Entra mapping and in the Select SCIM attribute dropdown.Can different automations read different attributes?
Can different automations read different attributes?
Does the mapping change the user's language, locale, name or cost center in SkillsDB?
Does the mapping change the user's language, locale, name or cost center in SkillsDB?
name.middleName, for example, does not change the person’s displayed name.Can I use a source other than the Entra hire date?
Can I use a source other than the Entra hire date?
extensionAttribute. SkillsDB only sees the spare attribute and the value in it, never where the value came from. The value must arrive as an ISO 8601 date; use an Expression mapping in Entra to reformat sources stored another way.Why did a user get the career but no initiation date?
Why did a user get the career but no initiation date?
Why did Restart provisioning not change a user's initiation date?
Why did Restart provisioning not change a user's initiation date?
Does this work with identity providers other than Entra?
Does this work with identity providers other than Entra?