# Leaver Workflow to schedule more Workflows

**URL:** <https://developer.sailpoint.com/discuss/t/leaver-workflow-to-schedule-more-workflows/187810>\
**Category:** IIQ Discussion and Questions\
**Tags:** workflows, rules, identityiq, aggregation, provisioning, apis\
**Created:** [November 10, 2025, 7:10am UTC](https://developer.sailpoint.com/discuss/t/leaver-workflow-to-schedule-more-workflows/187810 "2025-11-10T07:10:36Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rishavghoshacc](https://avatars.discourse-cdn.com/v4/letter/r/dc4da7/32.png) [@rishavghoshacc](https://developer.sailpoint.com/discuss/u/rishavghoshacc)\
**Post date:** [November 10, 2025, 7:10am UTC](https://developer.sailpoint.com/discuss/t/leaver-workflow-to-schedule-more-workflows/187810/1 "2025-11-10T07:10:36Z")

</div>

Hi all,

We have a requirement to implement LCM leaver workflow as follows:

1. first disable the account
2. After 24 hrs remove the roles
3. After 5 days we should delete the AD account

How can we achieve this?

Thanks in advance

---

<div class="post-metadata">

**Author:** ![kumarSinghM](https://avatars.discourse-cdn.com/v4/letter/k/ecb155/32.png) [@kumarSinghM](https://developer.sailpoint.com/discuss/u/kumarSinghM)\
**Post date:** [November 10, 2025, 7:25am UTC](https://developer.sailpoint.com/discuss/t/leaver-workflow-to-schedule-more-workflows/187810/2 "2025-11-10T07:25:15Z")

</div>

@rishavghoshacc Use the approach below:

1. In the Leaver workflow, disable the account. Once the Disable Account Step is completed, proceed to the next step to schedule a workflow after 24 hours for removing roles.
2. Once this is done, link it to another step to schedule a workflow that deletes the AD account after 5 days.

You need to use the Workflow Scheduler API for this.

---

<div class="post-metadata">

**Author:** ![santhirajumunganda](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/santhirajumunganda/32/42744_2.png) [@santhirajumunganda](https://developer.sailpoint.com/discuss/u/santhirajumunganda)\
**Post date:** [November 10, 2025, 1:21pm UTC](https://developer.sailpoint.com/discuss/t/leaver-workflow-to-schedule-more-workflows/187810/3 "2025-11-10T13:21:18Z")

</div>

Hi @rishavghoshacc you can easily achieve this because SailPoint provides this functionality by default.

Navigate to **Applications → Rapid Setup → Leaver Tab**

1. For **Disable Account** , you’ll see two options — **Now** or **Later**. In the **Later** option, you can simply specify the number of days.

2. For **Delete Account** and **Remove Roles** , follow the same approach as above.

3. Check the attached screenshot

4. 

 ![image](https://global.discourse-cdn.com/sailpoint/original/3X/b/a/ba5d82f4082345e841d475c046624fa6bc8bc7cd.png)

Thanks,  
Raju :expert_ambassador:

---

<div class="post-metadata">

**Author:** ![daniel\_neubert](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/daniel_neubert/32/714_2.png) [@daniel\_neubert](https://developer.sailpoint.com/discuss/u/daniel_neubert)\
**Post date:** [November 11, 2025, 8:00am UTC](https://developer.sailpoint.com/discuss/t/leaver-workflow-to-schedule-more-workflows/187810/4 "2025-11-11T08:00:20Z")

</div>

Hi @rishavghoshacc ,

just in case you already have a custom workflow for the Leaver use-case you will be able to easily achieve that goal by adding appropriate “wait”-steps.  
Otherwise the Rapid Setup approach is considered the most efficient approach.

Best regards,  
Daniel

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [January 10, 2026, 8:00am UTC](https://developer.sailpoint.com/discuss/t/leaver-workflow-to-schedule-more-workflows/187810/5 "2026-01-10T08:00:31Z")

</div>

Closed on January 10, 2026, 8:00am UTC

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
