Implementing an HR Identity Model
Key Takeaways
Connect and validate the authoritative source and its account data before relying on identity mapping outputs.
Create the identity profile with its required mappings before expecting authoritative records to become usable identities.
Prove a controlled HR load and review exceptions before configuring broad downstream access.
The Workday SaaS connector requires OAuth 2.0 and full aggregation for Pre-Hire records. Check population permissions and effective-date settings.
Start with the human resources data contract
An identity model turns approved human resources (HR) records into identities that can govern accounts and access. Start by recording the authoritative population, the expected unique user name, the minimum required identity data and the business fields needed for manager and lifecycle decisions. Ask which changes come from HR, which source owns each supplemental field, and how to handle people whose data arrives early or is incomplete. A procurement role is downstream of these facts. Activating that role before validating the identities could send access to the wrong accounts.
Use a small set of test records with expected outcomes. Include a current employee, a prehire, an account missing a required value and two workers with the same display name but distinct User Names (uid). Test duplicate uid separately. If two records map to the same User Name, expect an identity exception and trace the mapping back to its source value before changing any account-correlation rules. If a record already exists on another authoritative system, prepare an overlap case with independently confirmed correlation and expected precedence. Identify which step should produce each result so the team can diagnose a failure early.
Sequence the implementation
| Stage | Action | Evidence to retain |
|---|---|---|
| Define identity inputs | Verify authoritative populations and stable identifiers with the data owner | Example inputs and expected identity outputs |
| Configure the HR connection | Select the supported connector and variant, connect with approved access and test it | Successful credential and source path test |
| Review data shape | Inspect source attributes and select suitable Account ID and Account Name values before the intended load | Schema and a representative extraction or preview |
| Create the authoritative identity profile | Select the HR source and define required and business-critical attribute mappings | Expected values for at least one employee and one edge case |
| Load and validate | Aggregate a controlled population, review identities, identity exceptions and expected relationships | Matched account and identity records plus exception resolution |
| Validate dependent connections and policy | Configure target correlation, and stage and test lifecycle or role actions | Operation tracking and target-side proof of intended access |
The source provides accounts. The identity profile defines how the authoritative accounts populate identities. For an ordinary non-authoritative target, configure appropriate account correlation before its first production load, after confirming eligible identities exist to match to. Manager relationships also depend on a defined mapping and source correlation setting. Verify these with actual manager records rather than assuming that an HR manager field automatically creates the relationship. Defining the data and testing the layers in order does not prevent an iterative rollout. It gives each iteration a specific check.
Workday example
Suppose a company uses the Workday SaaS connector and needs to process new hires before the start date. For Workday Pre-Hire records from Recruiting, use OAuth 2.0 and a full aggregation. Confirm that prehire aggregation is in scope and that the Workday integration user has the extra Pre-Hire permissions. A future-dated worker record and a Recruiting Pre-Hire record are distinct populations in the connector documentation. Check the connector’s Effective Time Zone against how the HR system processes effective-dated changes. Use a full time-zone identifier such as America/Chicago when it matches the HR configuration. SailPoint documents that a mismatch can cause a future-dated worker to disappear in the aggregation before the hire date and reappear afterward. Reading active workers does not prove that prehire records are visible with the same authorization and timing.
If the connection test is successful and aggregation never returns the intended record, confirm which population it belongs to. Check the supported authentication and aggregation mode for Recruiting records, or the relevant filter, permissions and effective-date settings for future-dated workers. If the account is present but the identity construction fails, inspect the required mapping values and identity exception report. If the identity appears with the expected values but the directory account is missing, inspect the planned lifecycle or role and the provisioning result. The observed stage determines which evidence matters.
Validate the handoff to production
After a pilot run, compare actual source records with the tenant account list and the expected identities. If required identity values were missing, correct the underlying data or mapping and verify processing after another appropriate load. Confirm the intended state and manager link separately. Then test the actual target effects for an eligible worker and for a worker who must be excluded. The first successfully created identity proves that one input passed the model. Include the edge cases before expanding scope.
See SailPoint’s source configuration, identity profile setup, Workday SaaS permissions, connection settings, and aggregation troubleshooting.
An HR source connection and account schema have been validated. What should the engineer configure before the first controlled load intended to create usable identities?
The identity profile for the HR source and mappings for the required identity values
A role granting every employee application access
The service desk’s failure status mapping
The procurement directory’s account deletion threshold
The Workday SaaS connector’s delta job returns active workers but misses a Recruiting Pre-Hire record. What should the engineer verify first?
The provisioning task history for a downstream directory write
Whether an existing access profile has request approvals
OAuth 2.0, the Pre-Hire permissions and a full Workday aggregation
The ordering of two access certification reviewers
Sections you finish are checked off in the contents.