Study guide

5.4 Rapid Setup in Lifecycle Events and Identity Operations

SailPoint Certified IdentityIQ Engineer Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: The IdentityIQ Engineer Exam

1.1 Exam Format, Official Blueprint, and Study Strategy

2 Chapter 2: Infrastructure, Installation, and Extended Attributes

2.1 IdentityIQ Infrastructure Components 2.2 Installation Steps and Procedures 2.3 Creating Extended Attributes and the Objects That Support Them

3 Chapter 3: Build, Deployment, Patching, Access, and Email

3.1 Ongoing Build and Deployment 3.2 Installing Patches and Performing Upgrades 3.3 Configuring End-User Access 3.4 Email Server Settings and Email Redirection

4 Chapter 4: Lifecycle Manager Configuration, Provisioning Policies, and Workflows

4.1 Configuring Lifecycle Manager 4.2 Identity Provisioning Policies 4.3 Configuring LCM Workflows

5 Chapter 5: Lifecycle Events, QuickLinks, Batch Requests, and Rapid Setup

5.1 Lifecycle Events and Their Workflows 5.2 QuickLinks and QuickLink Populations 5.3 Configuring and Using Batch Requests 5.4 Rapid Setup in Lifecycle Events and Identity Operations

6 Chapter 6: Certification Campaigns and Certification Rules

6.1 Configuring and Scheduling Certification Campaigns 6.2 The Purpose of Common Certification Rules

7 Chapter 7: Policies and Policy Violations

7.1 Configuring and Leveraging Policies 7.2 Responding to Policy Violations

8 Chapter 8: Reporting, Advanced Analytics, and Auditing

8.1 Executing and Leveraging Reports 8.2 Leveraging Advanced Analytics 8.3 Configuring and Using Auditing

9 Chapter 9: Rules, Rule Libraries, and the SailPoint API

9.1 The Purpose and Use of Rule Libraries 9.2 Rule Input and Output Arguments 9.3 Common SailPoint API Objects and Methods

10 Chapter 10: Workflow Development

10.1 Workflow Variables, Transitions, and Step Conditions 10.2 Workflow Steps That Generate Work Items 10.3 The Different Workflow Step Usages 10.4 Leveraging Sub-Workflows

11 Chapter 11: Email Templates, Branding, and Localization

11.1 Customizing and Using Email Templates 11.2 Branding the SailPoint User Interface 11.3 Localizing the SailPoint UI

12 Chapter 12: Application Definitions, Connector Settings, and Rapid Setup Aggregation

12.1 Configuring Application Definitions 12.2 Configuring Common Connector Settings 12.3 Configuring Rapid Setup Aggregation Settings

13 Chapter 13: Data-Loading Tasks and Application and Connector Rules

13.1 Scheduling Tasks for Data Loading and Processing 13.2 Common Application Rule Types 13.3 Common Connector Rule Types

14 Chapter 14: Debugging with log4j, Syslog, and the IdentityIQ Console

14.1 Configuring and Leveraging log4j 14.2 Configuring and Leveraging Syslog 14.3 Leveraging the IdentityIQ Console for Debugging

15 Chapter 15: Debug Pages and the Administrator Console

15.1 Leveraging the Debug Pages for Debugging 15.2 Leveraging the Administrator Console for Debugging

16 Chapter 16: Role Model and Identity Attribute Mappings

16.1 Default Role Models and Role Types 16.2 Configuring Roles and Role Options 16.3 Configuring Identity Attribute Mappings

17 Chapter 17: Data Objects, Relationships, and Group Types

17.1 Common IdentityIQ Data Objects 17.2 Relationships Between Common Data Object Models 17.3 The Difference Between Group Types

5.4 Rapid Setup in Lifecycle Events and Identity Operations

Key Takeaways Explain This Topic AI

Rapid Setup comes with Lifecycle Manager and is configured globally on Global Settings > Rapid Setup Configuration, with Joiner, Mover, Leaver, Identity Operations, and Miscellaneous tabs.

Per-application behavior is set on Applications > Rapid Setup, and each process must be enabled globally first.

Trigger filters should detect a change (for example, "Inactive Changed to True") rather than a state ("Inactive Equals True").

Leaver takes priority over joiner and mover, and joiner takes priority over mover.

Immediate termination without approvals is started from Identities > Identity Operations, one identity at a time, with a required reason.

Last updated: September 2026

Rapid Setup in Lifecycle Events and Identity Operations

Objective 2.7 asks you to leverage Rapid Setup in lifecycle events and identity operations . Rapid Setup is included with Lifecycle Manager , so there is nothing separate to install. It gives business users a guided way to define joiner, mover, leaver, and termination behavior. It does not replace native lifecycle events (section 5.1). It is an alternative, centralized way to configure them with preconfigured, best-practice business processes such as RapidSetup – Joiner , Mover , and Leaver .

Rapid Setup separates technical onboarding (connection parameters and schema, done first in Application Definition) from business onboarding (what happens to accounts when people join, move, or leave).

Global Configuration

Go to gear icon > Global Settings > Rapid Setup Configuration . Each tab has an enable slider. A dot on a tab means unsaved changes, and a checkmark on the dot means the changes are saved.

Joiner Tab

Generate Approvals. The default RapidSetup – Joiner process delegates approvals to LCM Provisioning .

Automatically Join New Empty Identities includes new identities with no accounts and bypasses trigger filters for them.

Exclude Uncorrelated Identities. A correlated identity has an account on an authoritative application.

Alternative Workgroup for the Joiner Completed email, a Joiner Completed Notification Email Template , and Send Temporary Password Email .

Post Joiner Rule (rule type PostLifecycle ), Threshold Type/Threshold , Joiner Business Process , and Trigger Filters .

Mover Tab

Launch a Targeted Certification of the mover's access. The new manager is the default certifier, and you can Include Previous Manager as a Certifier . You can also stage the certification, include birthright roles, set a certification owner, and set a backup certifier. If joiner processing is part of the move, the certification must complete before joiner processing starts.

Joiner Processing re-applies birthright roles and account-only provisioning as part of the move.

Post Mover Rule , threshold, business process, and a trigger filter that defines what a "move" is, such as Manager Changed .

Leaver Tab

Remove Assigned Roles and Reassign Artifacts , such as applications, workgroups, and policies owned by the leaver. Reassignment goes to the manager, then a rule, then an alternate.

Reassign Identities , such as service accounts and RPA or bot identities the leaver administers.

A notification workgroup, the reassignment and completed email templates, Post Leaver Rule (type LeaverReassignment ), threshold, business process, and trigger filter.

Identity Operations and Miscellaneous Tabs

Identity Operations enables Terminate Processing with the same reassignment options, a Terminate Business Process , and a Post Terminate Rule .

Miscellaneous sets the Business Process Requester (for auditing), the RapidSetup No Manager workgroup, the Rapid Setup Error Notification workgroup, email style sheet, header, and footer templates, and the role types treated as birthright roles (default type rapidSetupBirthright ).

Trigger Filters: The Most Tested Idea

Trigger filters decide which identities each process acts on. They use identity attributes or saved populations with AND/OR groups. The documentation stresses:

Use change operators. "Inactive Equals True" selects every inactive identity on every run. "Inactive Changed to True" selects only identities that just became inactive.

Date criteria fire at midnight local time on the specified date. Populations built in Advanced Analytics can exclude groups, such as executives, from standard mover processing.

Event Priority

  • If an identity qualifies for… Rapid Setup launches
  • Leaver and joiner Leaver only
  • Leaver and mover Leaver only
  • Joiner and mover Joiner only
  • Per-Application Settings (Applications > Rapid Setup)

Joiner: Perform Account-Only provisioning , which creates an empty account even with no entitlements. Identity Selection can be Everyone, Filter, Script, a Rule (type IdentitySelector), or a Population. You can also Automatically Start Joiner Processing for Newly Created Identities during aggregation and add email instructions.

Mover: include additional entitlements or targeted permissions in the certification, and account-only provisioning.

Leaver: either Use rule (one rule handles leaver and termination) or Configure the actions: Delete Account , Disable Account , Scramble Password , Move Account (Active Directory OU only), Remove Entitlements with exceptions, and Add Comment . Each can run Now or Later , after a number of days. Termination can reuse the leaver settings or have its own. Create the provisioning policies needed for delete, disable, and unlock, plus a password policy for scrambling, before configuring leavers.

Immediate Termination

Go to Identities > Identity Operations .

Select one identity.

Choose Terminate and enter the required reason .

Review and Submit . The leaver-style termination runs immediately without approvals .

How Rapid Setup Connects to Lifecycle Events

Rapid Setup processing still runs through identity refresh . The Lifecycle Events page includes a Rapid Setup event type that launches a Rapid Setup business process when the selected RapidSetup process is detected. So the same scheduling rule applies as for native events: aggregate the authoritative source, then run Identity Refresh with Process Events . The exception is the joiner option Automatically Start Joiner Processing for Newly Created Identities , which starts joiner processing during aggregation when a new identity is created.

When should you use Rapid Setup instead of hand-built lifecycle events? Rapid Setup fits standard joiner, mover, and leaver patterns that business users need to maintain per application. Custom lifecycle events and workflows fit unusual logic, such as a reinstatement process with custom approvals. Both can exist in one installation.

Safety Net: Identity Processing Thresholds

A fixed or percentage threshold on joiner, mover, or leaver processing stops the Identity Refresh task before it updates anyone when too many identities qualify. Process events must be enabled in the refresh for the threshold to apply. For troubleshooting, set the sailpoint.rapidsetup and sailpoint.workflow.RapidSetupLibrary loggers to debug in log4j2.properties . Sample rules are in WEB-INF/config/rapidsetup/rsexamplerules.xml .