Configuring and Testing Manager Correlation
Key Takeaways
Map Manager Name in the identity profile and configure Manager Correlation on the source that supplies the employee’s manager identifier.
Match the employee account’s manager identifier to the designated attribute on the manager’s identity.
SailPoint checks profile mappings by priority and uses the first source that provides a non-null manager value.
A changed value that cannot be resolved can leave the existing manager link. Verify actual relationships before relying on manager approvals.
Distinguish the two links
Account correlation associates an outside account with the identity that owns it. Manager correlation associates an employee identity with their manager’s identity. An employee can have a correctly linked account while having no manager link. That difference affects manager approvals and manager certifications. If an access review expects a manager, verify the link in the identity data before assuming the employee’s underlying account association proves it.
Configure both layers of manager correlation. In the identity profile, map the Manager Name attribute to the source account field that contains the employee’s manager identifier. On that source, open its account correlation settings and use the Manager Correlation section to pair the account attribute with an identity attribute. The account-side value comes from the employee’s source account. The identity-side value is found on the manager’s identity. In a basic case, the manager’s own identification number supplies a stable match. If the matching identity field is custom, check that it has been made searchable for correlation using the documented identity-attribute configuration. That setting has a different purpose from the general Search page.
| Value needed | Example | Location |
|---|---|---|
| Employee’s manager reference | supervisorNumber=M204 | Employee’s HR source account |
| Matching value on an existing manager identity | identificationNumber=M204 | Manager’s identity attribute |
| Manager shown for the employee | Link to the identity whose number is M204 | Computed manager relationship |
| Employee account ownership | Account matched by the employee’s own worker identifier | Separate account correlation |
Apply source and priority rules
SailPoint considers identity profiles in priority order for manager correlation and uses the first mapped source that has a non-null manager value. Keep the lower numeric value and higher precedence relationship in mind. This logic tests the available manager input. It is different from choosing one owning identity profile for the person’s other mappings.
For example, suppose eligible profiles with priorities 10 and 20 have manager mappings available for the worker. The first source’s manager field is null and the second source supplies M204. The second source provides the candidate value for manager correlation. The configuration on that source must still identify the manager attribute, and an actual identity must have the matching value. A non-null input is the beginning of a lookup. Suppose the intended manager is present as a directory account but their identity has no identificationNumber. Before changing the employee’s supervisorNumber, trace why M204 was not promoted to the manager identity. When the intended manager has M204 and verifies as the unique match, confirm the employee’s Manager link points to that identity. The manager’s directory account by itself is insufficient evidence for this match.
If the employee switches supervisors, test both a correct changed value and an unresolvable change. SailPoint documents that an account attribute changing to a value that cannot match a new manager can leave the existing manager in place. If the value instead changes to null and no other usable manager mapping applies in the case, the relationship can become null. Check the source and the existing manager separately before closing a stale-manager incident.
Verify a change with real records
- Confirm that the correct employee and manager identities exist and compare their source values.
- Verify the profile’s Manager Name mapping and the matching source configuration.
- Trigger the appropriate aggregation or identity processing for the relevant changes.
- Inspect the linked manager on representative employee records. Test the specific approval or certification workflow that consumes it.
A complex use case, such as choosing the correct manager input when an identity has multiple authoritative accounts and only one is active, may require a Manager Correlation Rule. SailPoint provides a separately documented cloud rule for such cases. First check whether the standard mapping and correct source data can express the requirement. For a rule, verify representative accounts and edge cases. This rule runs before configured manager correlation and returns the identity attribute name and value to identify the manager, such as identificationNumber and M204. A rule for a general identity attribute returns the attribute value directly instead.
See SailPoint’s manager correlation configuration, identity processing, and Manager Correlation Rule.
An employee account’s supervisorNumber is M204. The manager identity uses identificationNumber M204. What configuration creates the relationship?
Pair the two fields in the employee’s own account ownership rule only
Map Manager Name from supervisorNumber and configure the source’s manager pairing to the manager identity’s identificationNumber
Map both fields to the employee’s display name and change their sign-in format
Set the supervisor’s role priority to 204
There is one applicable manager data source. An employee already has a linked manager. The source changes the manager field to a non-null identifier that does not match any manager identity. What should the engineer anticipate?
The old manager identity is deleted
The employee’s source account is automatically uncorrelated
SailPoint creates a manager identity from that field alone
The previous manager can remain linked until the data issue is resolved
Sections you finish are checked off in the contents.