Designing Lifecycle States from Requirements
Key Takeaways
Define lifecycle states per identity profile, and map Lifecycle State to the enabled state’s exact technical name.
Use lifecycle states for employment-stage behavior and role criteria for access conditions that can change while employment status stays the same.
Choose an identity state separately to control participation in platform processes.
Verify which selected sources and connectors support the required account action. One source cannot have multiple account actions in the same lifecycle state.
Start with policy decisions
An identity’s lifecycle state describes its status under the organization’s access policy. Define states within an identity profile. Each identity is in one lifecycle state at a time. A state can grant access profiles, remove access under configured rules, enable or disable supported source accounts, and send notifications. Start with when the business wants each behavior to apply and what evidence establishes that the state is appropriate. Then choose mappings and account actions.
SailPoint provides prehire, active, leave of absence, terminated, and archived states for new profiles. Organizations can define additional states. Check the state’s technical name and whether the state is enabled before assuming a mapping can assign it. The mapped Lifecycle State attribute, cloudLifecycleState, must match the technical name’s case. If a source says ON_LEAVE but the profile uses a different technical name, apply a supported transform to convert it to the exact name. Preview the mapped result before applying changes.
| Requirement | Configuration decision |
|---|---|
| Keep an employee’s ongoing lifecycle status while reallocating department access | Keep the lifecycle state if employment status has not changed and use appropriate role membership criteria for the new department |
| Apply a distinct account action to a defined absence | Represent it with an enabled lifecycle state when its timing and access policy differ |
| Permit some temporary access while restricting another source | Use deliberate profile grants and selected source actions, verifying both source lists and retention effects |
| Keep an archived identity out of certain platform processes | Consider the appropriate underlying identity state and its functional effects |
| Remove an account on a designated source after an approved point | Verify supported deletion, Inactive (long-term) identity state, and the specific source rather than All sources |
The identity state in Lifecycle Management is a separate choice from the employment-stage label. SailPoint describes Active, Inactive (short-term), and Inactive (long-term), with different participation in platform functions. For example, choosing Inactive (long-term) has implications for scheduled identity processing and attribute synchronization. A business label such as “On Leave” does not itself tell the system to disable an account or to exclude it from a process. Assign the underlying identity state and actions deliberately.
Worked leave and mover design
A company wants active Procurement workers to keep the same overall lifecycle state when they transfer to Finance. The new department should change their department-based application access. In the design, the authoritative department value and applicable role criteria govern that switch. Keep the active lifecycle state for baseline access and unrelated account behavior. Test that old department membership is removed according to role assignment behavior and the intended new membership is applied. An identity profile for each department would create another source-ownership question without expressing this requirement.
Now consider a leave of absence that should disable one directory account temporarily and keep access to an employee portal on a different source. Use a leave state with the appropriate actions and explicit target source selection. Verify the directory connector supports disabling and re-enabling the relevant account. Check that any access profile granted by the leave state does not belong to the directory source intended for disablement, because SailPoint documents protection against disabling or deleting a source account when that source includes an access profile granted in the state. At return, assess which access profiles remain the same and which actions must restore target access. If the policy also requires manager notice at the state change, select Manager in the state’s Email Notification List. Validate the worker’s manager relationship and verify the chosen recipient in a leave test. Check the directory account’s resulting status independently of whether the message arrives.
Reject conflicting actions before activation
A source cannot be configured for multiple account operations in the same state. When the requirement includes disabling at leave and enabling at return, put those actions in their respective enabled states. Avoid a blanket action where the policy calls for a targeted one. For deletion, select the allowed specific source and only when the state and connector support it. Review a vendor’s target permissions as well as the tenant setting. A valid design requires both a correct state calculation and an executable access plan.
See SailPoint’s lifecycle state configuration, identity states, identity processing, and automatic role assignment.
An active employee transfers from Procurement to Finance but remains employed under the same account policy. Only department-based access should change. Which design fits?
Create a new authoritative source for each department
Set the identity to Inactive (long-term) during every transfer
Delete the account and recreate it whenever its department changes
Keep the active lifecycle state and reevaluate department-based role criteria from the mapped department
A lifecycle state is enabled with technical name leavePaid. The Lifecycle State attribute returns leavepaid. What change makes the automatic assignment valid?
Choose any display title that starts with leave
Map the attribute to the exact technical value leavePaid
Configure both disable and delete for the same source
Set the identity profile priority to a negative number
Sections you finish are checked off in the contents.