Configure a lifecycle event
Quick answer
Step-by-step: configure a joiner, mover or leaver lifecycle event in SailPoint IdentityIQ.
Key takeaways
- Events fire on identity change (joiner/mover/leaver)
- Define the attribute condition or rule
- Point the event at a provisioning workflow
- Test by changing data and running refresh
1. Define the trigger
A lifecycle event fires on an identity change, for example a new identity (joiner) or a change to department or manager (mover), or inactivation (leaver).
2. Set the condition
Specify the attribute condition that identifies the event, using an identity filter or a rule for complex logic.
3. Choose the workflow
Point the event at the workflow that should run, typically an LCM provisioning workflow that grants or revokes access.
4. Test with refresh
Trigger the event by changing test data and running identity refresh, then confirm the workflow provisioned correctly.
Want to learn this properly?
Our live, instructor-led SailPoint Training covers this hands-on, with real projects and a certification path.
Check your understanding
What detects and fires a lifecycle event?
- A. Aggregation only
- B. Identity refresh matching the event condition
- C. The connector
- D. A report
Show answer
B. Identity refresh matching the event condition
Identity refresh detects the attribute change and fires the matching lifecycle event.