# Workflow to enable Disabled account

**URL:** <https://developer.sailpoint.com/discuss/t/workflow-to-enable-disabled-account/197416>\
**Category:** SHF Discussion and Questions\
**Tags:** identity-security-cloud, workflows, provisioning\
**Created:** [February 25, 2026, 11:53pm UTC](https://developer.sailpoint.com/discuss/t/workflow-to-enable-disabled-account/197416 "2026-02-25T23:53:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mtavan](https://avatars.discourse-cdn.com/v4/letter/m/f08c70/32.png) [@mtavan](https://developer.sailpoint.com/discuss/u/mtavan)\
**Post date:** [February 25, 2026, 11:53pm UTC](https://developer.sailpoint.com/discuss/t/workflow-to-enable-disabled-account/197416/1 "2026-02-25T23:53:06Z")

</div>

> ‼ Please be sure you’ve read the [docs](https://developer.sailpoint.com/idn/docs/) and [API specs](https://developer.sailpoint.com/idn/api/getting-started) before asking for help. Also, please be sure you’ve [searched](https://developer.sailpoint.com/discuss/search?expanded=true) the forum for your answer before you create a new topic.

## Hello Sailpoint Community.

I have switched to ISC work recently and i’m trying to find a way to check inside the workflow if a specific account from a specific source is disabled at the moment the provisioning (add operation) happens for a particular source, basically when a user requests a access for that source, we need to check if the account is disabled and if its, we need to enable. Thats pretty much the business requirement since we have a particular system that disables their accounts automatically when user does not log into it for some time.

i’m trying these approaches

$.loopThroughAccounts.loopInput.disabled = true

$.loopThroughAccounts.loopInput.sourceName = AD - Test

But i’m not sure this is the right approach, currently not working.

Whats the proper way to access and compare an Account existing attribute?

Going to add the json as well.

[EnableAccountWorkflowjson.json](https://developer.sailpoint.com/discuss/uploads/short-url/gie8LleJmvRlNTLPbkgQ2hRmoo8.json) (3.6 KB)

 ![image](https://global.discourse-cdn.com/sailpoint/original/3X/0/5/0532c6d51cb2dbab3d7390f55d292cbbc01236c8.png)

 ![image](https://global.discourse-cdn.com/sailpoint/original/3X/0/4/0492e602b4c0f1924a85417ed784318a44c9f2dc.png)

 ![image](https://global.discourse-cdn.com/sailpoint/original/3X/7/6/76f98306cb6416ca465fbe524ccd26fb9f6988b0.png)

---

<div class="post-metadata">

**Author:** ![Tulasi](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/tulasi/32/34596_2.png) [@Tulasi](https://developer.sailpoint.com/discuss/u/Tulasi)\
**Post date:** [February 26, 2026, 8:11am UTC](https://developer.sailpoint.com/discuss/t/workflow-to-enable-disabled-account/197416/2 "2026-02-26T08:11:01Z")

</div>

Hi @mtavan  
In the Workflow inside loop you have given the compare string and compare boolean  
value 1 wrong I have updated that in this below workflow, Please check it once

[EnableAccountAfterAccessRequest20260226.json](https://developer.sailpoint.com/discuss/uploads/short-url/8k1imkKxDV9flHDpbFWq9DQgoRe.json) (3.7 KB)

Thanks & Regards  
Tulasi

---

<div class="post-metadata">

**Author:** ![mtavan](https://avatars.discourse-cdn.com/v4/letter/m/f08c70/32.png) [@mtavan](https://developer.sailpoint.com/discuss/u/mtavan)\
**Post date:** [February 26, 2026, 6:51pm UTC](https://developer.sailpoint.com/discuss/t/workflow-to-enable-disabled-account/197416/3 "2026-02-26T18:51:23Z")

</div>

Thanks, this json helped me fixing one of the issues, now it seems to be working.

---

<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:** [April 27, 2026, 6:51pm UTC](https://developer.sailpoint.com/discuss/t/workflow-to-enable-disabled-account/197416/4 "2026-04-27T18:51:38Z")

</div>

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