Each user's manager can be synchronized automatically from SCIM, LDAP, Google Workspace, API synchronization, and a CSV file. This article explains how it works for each channel and what to keep in mind to avoid losing assignments.
What changed?
The manager is now synchronized through SCIM, LDAP (with the new Manager attribute), Google Workspace, and API synchronization.
Each channel manages the field. What the channel reports replaces the recorded manager, even when it was manually edited on the user.
Where is it configured?
- Synchronization is configured under People > User import and synchronization.
- The manager is manually edited under People > Users.
| Requirement: you must have user synchronization configured through the corresponding channel. In LDAP, you must also complete the Manager attribute. |
How is the manager reported in each channel?
- SCIM and Google Workspace: the manager comes from the identity provider or directory. No additional configuration is required.
- LDAP: under People > User import and synchronization > From LDAP directory, complete the Manager attribute in the attribute mapping.
- API: under People > User import and synchronization > From API, add the manager mapping entry to the synchronization settings.
- CSV file: include the Manager Email column with the manager's email address to assign the manager. Leave it blank to remove the manager.
- Manual editing: you can edit the manager on the user under People > Users. The next synchronization through the channel replaces it.
Frequently asked questions
I manually edited the manager. Why did it change?
A manually edited manager is not protected. The next synchronization from any channel replaces it with the value reported by that channel.
| Important: if you need to preserve a change, make it at the source (identity provider, directory, API, or CSV file), not on the platform. |
Why did users end up without a manager after synchronization?
The manager for processed users is cleared in these cases:
- LDAP: the Manager attribute is empty.
- API: the synchronization settings do not have the manager mapping entry.
- CSV file: the file does not include the Manager Email column.
Does the order of the rows in the CSV file matter?
Yes. Rows are processed in order. If the manager appears below their subordinate, the manager does not yet exist when the subordinate is processed.
| Recommendation: place managers before their subordinates in the file. |
The order does not matter in LDAP and Google Workspace.
What happens if the manager's email address does not correspond to any user?
The platform removes the manager from that user and reports it as a warning in the synchronization results.
What happens if I deactivate a manager?
The relationship with their team is preserved. Only the manager's permanent deletion removes it.
| Note: the deactivated manager continues to receive their subordinates' emails and interactions. |
💡 Best practices
- Define a single channel as the source for the manager and keep the information updated there.
- Before enabling LDAP or API synchronization, confirm that the Manager attribute or mapping entry is configured. This prevents clearing the manager for all users.
- In the CSV file, order the rows hierarchically: managers first, followed by their teams.
- Review the warnings from each synchronization to identify manager addresses that could not be resolved.
- If a manager leaves the organization, reassign their team before deactivating them so that emails and interactions reach the right person.