2.4 Employee and Contractor Profile Precedence
Key Takeaways
Use a distinct identity profile for each authoritative source whose accounts are used to create identities.
An identity has one owning profile, even if the person has correctly correlated accounts on more than one authoritative source.
Lower numbers indicate higher profile priority. Decide priority from the business rule for overlapping accounts.
A profile’s priority and an individual attribute’s mapping are separate configuration decisions.
Decide where identities originate
A profile design starts with an inventory of people and account sources. Identify who supplies employee records, who supplies non-employee records, and whether those populations overlap. Some organizations keep the entire workforce in one authoritative system. Others load employees from human resources (HR) and contractors from a separate vendor management system. If both separate sources create identities from their own accounts, plan an identity profile for each. Other accounts may be correlated from sources that only provide access or information.
Choose authoritative sources because of the records and responsibilities they carry. A source can supply a contact attribute used by another profile without being the authoritative origin of that identity. Avoid creating a new identity profile solely to pull a value from a third system. Document which population relies on each source, which system owns each input, and what identifiers are available to distinguish one person from another.
Resolve overlap explicitly
SailPoint associates an identity with the highest-priority identity profile for which the person has an account on the authoritative source. A single identity has one profile even when more than one authoritative account is linked to it. Priority here is numeric. SailPoint’s documented default gives the first created profile priority 10, the next priority 20, and higher precedence to the smaller number. The identity profile update application programming interface (API) can change the priority. Set or verify the values before enabling automation that depends on profile selection.
| Account evidence for Lee | Configured profile priorities | Owning profile |
|---|---|---|
| Only a contractor account | Employee 10, contractor 20 | Contractor |
| Correctly linked employee and contractor accounts | Employee 10, contractor 20 | Employee |
| Correctly linked employee and contractor accounts | Employee 30, contractor 20 | Contractor |
| Only an employee account | Employee 30, contractor 20 | Employee |
The table assumes Lee has one identity and that the records shown are correctly linked. If two accounts have no reliable identifier in common, the priority comparison does not resolve whether they belong to one person. Validate the account-to-identity match separately. In a contractor conversion, a reused display name is weak evidence that two records represent the same person. Verify an identifier approved for cross-source identity matching.
Apply the business rule to a conversion
Suppose a company wants the employee profile to govern a person after their authoritative HR employee record is loaded and linked, even during an overlap when the contractor record remains. Give the employee profile higher priority and test the overlap before rolling out. Use a mock contractor account and an HR account with a confirmed match. Verify the owning profile and the actual lifecycle data selected for the identity. A separate contractor may have a similar display name and should stay associated with their own identity.
Now suppose company policy requires the contractor profile to win while both records are present. Prioritize that profile, then test the overlapping population again. Changing priority can affect multiple identities. Test unrelated employee-only and contractor-only records as controls. Their candidate profiles depend on which authoritative accounts they have. A different default creation order should not override the intended business decision.
If an authoritative account is deleted as part of an applicable account aggregation and the identity has an eligible account on a lower-priority authoritative source, SailPoint documents reassignment and recalculation of attributes from the remaining profile. Verify the exact deletion workflow and the resulting identity before using this behavior to implement a population transition. If aggregation does not remove the old authoritative account, the premise for that reassignment is absent. If it removes the account and no other authoritative source applies, SailPoint can attempt to delete the identity in a nightly job. Conditions such as source ownership or being another identity’s manager can block that identity deletion and leave a hidden identity.
Check owning profile and field values separately
After choosing the owning profile, its mappings govern identity attribute population. An employee profile can use a directory account as the input to its work email. Precedence decides which profile applies. The mapping decides what input supplies that field. Test these two results independently, along with any lifecycle and provisioning behavior that depends on the fields.
See SailPoint’s authoritative source priority and mappings, identity profile update API, non-employee profiles, and authoritative account deletion.
An identity has confirmed, correlated accounts on two authoritative sources. The employee profile has priority 10 and the external worker profile has priority 20. Which profile owns the identity?
The external worker profile because 20 is larger
Both profiles apply and alternately control attributes
The profile whose source performed its latest aggregation
The employee profile because 10 has higher precedence than 20
The selected employee profile should use the employee HR record for last name and a correlated directory account for work email. Which configuration fits?
Make the directory authoritative first solely so it can provide the email value
Use field-specific mappings in the employee profile and verify the directory account supplies email
Set the employee and directory profile priorities equal so each selects an attribute
Change the directory’s Account ID to the email address
Sections you finish are checked off in the contents.