Problem
- I integrated with SCIM and some fields are locked now.
- If I integrate with SCIM, which fields will lock?
- Can I update locked fields via CSV if they aren't mapped in my SCIM integration?
- What happens if I update locked fields that are mapped? Ones that actively receive data syncs from SCIM.
Resolution
Fields locked specifically due to SCIM being enabled will show a small "i" icon next to the field. Hovering over that icon will show a banner saying Synced with SCIM.Additional info:
-
- It is not possible to change which fields are locked/unlocked unless you disable your SCIM integration.
- These are the same for all of our SCIM integrations, regardless of the HRIS (for example, Okta SCIM behaves the same as Azure Active Directory SCIM when it comes to which fields are locked versus unlocked)
- For fields that are locked, these will remain locked even if the corresponding field in your HRIS is not mapped to send data to Lattice. This is a result of how the integration system was built and cannot be changed.
- As long as these fields are not in the list of attributes at all in your HRIS, you can update the field data via CSV upload and it will not be overwritten by future SCIM syncs.
- For fields that are unlocked, these will remain unlocked in user profiles even if they are mapped within your HRIS. This is also a result of how the integration system was built and cannot be changed.
- If data is input manually via the Lattice user profile into one of these unlocked but mapped fields, the SCIM sync will overwrite the data that was manually input.
Rundown of all fields and their locked/unlocked status once integrated with SCIM
- Preferred full name = unlocked
- Preferred display name = unlocked
- Pronouns = locked (but not due to SCIM)
- Preferred Language = locked (but not due to SCIM)
- HRIS full name = locked (due to SCIM technically, but is always locked regardless)
- External User ID = locked (due to SCIM technically, but is always locked regardless)
- Email address = locked
- Phone number = locked
- Job title = locked
- Department = locked
- Manager = locked
- Start date = locked
- Time zone = unlocked
- Birth date = locked
- Bio = unlocked
- Job type = unlocked
- Job level = unlocked
- Job function = unlocked
- Track = locked (but not due to SCIM)
- Track level = locked (but not due to SCIM)
- Gender = locked (see note below)
- Ethnicity / Race = unlocked
- Sexual Orientation = unlocked
- Note: Currently, our SCIM integrations aren't built to bring over the DEI attributes. However, Gender is an exception here because it was originally not categorized as a DEI attribute.
- Custom Fields = unlocked