Designing Joiner and Leaver Actions
Key Takeaways
Prehire and hire may have different allowed access. Specify which profiles, accounts and notifications each state should affect.
A lifecycle access profile is enforced while an identity remains in that state and is revoked on exit unless the new state also grants it.
Remove all access can leave birthright role access and profiles granted by the current state. Check each retained path.
Lifecycle account deletion requires the relevant Inactive (long-term) state, a supported connector and specific source selection.
Translate the dates into explicit outcomes
A joiner or leaver case often provides an effective date and lists which systems should be reachable at each stage. Start by mapping the business stages to the identity profile’s enabled lifecycle states. For prehire, the organization might allow an onboarding site but no main application access. On hire day another state can retain that site and grant normal baseline access. For termination, choose the supported account disables and access removals. Plan any later deletion separately and only where the policy and connector allow it.
This example assumes a worker starts April 11, is terminated effective July 3, and may have a designated application account deleted on August 3. Treat the date action as inclusive in this example and assume the relevant identity processing has run on each date. These dates are inputs to the example’s policy. SailPoint does not prescribe that interval between disablement and cleanup.
| Evaluated date | Assigned state in the example policy | Intended behavior |
|---|---|---|
| April 10 | Prehire | Onboarding profile only |
| April 11 | Active | Onboarding profile plus baseline work access |
| July 3 | Terminated | Disable the specified operational directory account and remove access subject to documented exceptions |
| August 3 | Archived | Inactive (long-term) with a supported, specifically selected application account deleted after checks |
Predict the effective access
A profile granted by the lifecycle state is enforced during that state. Removing it ad hoc while that state still governs the identity can lead to it being provisioned again. On leaving a state, SailPoint revokes the profile granted by that state unless the new state also grants it. In the example, the onboarding profile is granted in both prehire and active. It stays assigned through that transition. The baseline work profile enters with active under the stated policy. Verify whether a target account is created or modified based on the connector’s support and the user’s existing accounts.
For termination, inspect each reason access is present. SailPoint’s Remove all access setting can revoke roles, access profiles and entitlements and bypass removal approval. SailPoint enables this setting by default for its Terminated and Archived states. The documented exceptions include access from birthright roles and access profiles provisioned by the current state. If a birthright role still includes the worker, revise the role criteria or applicable assignment before concluding that all target access has gone. A profile explicitly granted in the terminated state is another intentional retention path. When a source includes a profile granted by the current lifecycle state, SailPoint’s documentation excludes that source account from disablement or deletion. Check that any retained-access exception sits on the intended source. In this case, a restricted post-employment portal belongs on a different source from the operational directory the employer must disable. Verify both actions against the same terminated test identity. A directory-backed profile granted in Terminated could defeat the expected disablement even though the account action appears correctly configured.
Stage disablement and deletion
Disabling a source account is different from deleting it. Review which source supports each operation and verify the connector’s permissions. SailPoint allows lifecycle account deletion only when the underlying identity state is Inactive (long-term) and specific sources are selected. The All sources option is available for enable or disable, not for delete. The same source cannot be selected for multiple operations under the same lifecycle state. If access from an active role still needs a deleted account, SailPoint documents that a later identity refresh can recreate the account. Confirm that the assignment was removed when account recreation would violate the design.
In this example, choose Inactive (short-term) for Terminated if the person must still be eligible for a later scheduled calculation into Archived under the tenant’s processing settings. Inactive (long-term) is excluded from ordinary scheduled processing. If a design calls for an earlier move to long-term, choose and test a supported trigger for the later transition, such as targeted manual processing.
Verify the actual result at each step. When the person enters terminated, check the tenant state, launch and completion of provisioning, and the operational directory’s real account status. Perform the separate archived check before expecting deletion. A mapped change that has been calculated correctly can still be followed by an unsuccessful target action. Capture the target-side evidence instead of treating the changed state as proof of fulfillment.
See SailPoint’s lifecycle actions, grants and exceptions, identity state eligibility, and processing and outcome verification.
A worker moves from an enabled Prehire state to an enabled Active state. Both states grant the same Onboarding access profile, and no other rule changes it. What is the expected lifecycle effect?
The profile remains assigned because the new lifecycle state also grants it
The profile must always be revoked between the states
The identity becomes uncorrelated before the grant can run
Prehire’s grant blocks all new Active state grants
A Terminated state has Remove all access enabled. The worker still meets a birthright role assignment and the Terminated state grants a distinct restricted profile. Which access can remain under the documented exceptions?
Only the worker’s expired access requests
Only the employee’s previous manager approvals
Access from the qualifying birthright role and the current state’s profile
No access, because that toggle guarantees every target entitlement is removed
Sections you finish are checked off in the contents.