# How to make Entitlement requestable "true" during AD group aggregation **URL:** \ **Category:** SHF Discussion and Questions\ **Tags:** aggregation, sailpoint-identity-security\ **Created:** [June 19, 2025, 11:21pm UTC](https://developer.sailpoint.com/discuss/t/how-to-make-entitlement-requestable-true-during-ad-group-aggregation/146364 "2025-06-19T23:21:18Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![tsandeepsTDC](https://avatars.discourse-cdn.com/v4/letter/t/bc79bd/32.png) [@tsandeepsTDC](https://developer.sailpoint.com/discuss/u/tsandeepsTDC)\ **Post date:** [June 19, 2025, 11:21pm UTC](https://developer.sailpoint.com/discuss/t/how-to-make-entitlement-requestable-true-during-ad-group-aggregation/146364/1 "2025-06-19T23:21:18Z")
## Please consider addressing the following when creating your topic: - What have you tried? AD group aggregation. Entitlement created with non requestable. - What errors did you face (share screenshots)? requestable is false. - Share the details of your efforts (code / search query, workflow json etc.)? - What is the result you are getting and what were you expecting? During group aggregation or any auto process want to set requestable to true for all entitlements. There is option to make requestable to true by UI, but this manual process, i am looking auto process. ---
**Author:** ![punna0001](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/punna0001/32/42011_2.png) [@punna0001](https://developer.sailpoint.com/discuss/u/punna0001)\ **Post date:** [June 19, 2025, 11:52pm UTC](https://developer.sailpoint.com/discuss/t/how-to-make-entitlement-requestable-true-during-ad-group-aggregation/146364/2 "2025-06-19T23:52:36Z")
Hello Sandeep, **This is what I found:** By default, **SailPoint ISC’s AD group aggregation** does not automatically set `requestable = true` on imported entitlements (such as AD groups). The **UI option** (editing individual entitlements to set `requestable = true`) is manual and not scalable for large environments. **You can try this:** Since aggregation itself doesn’t have a built-in setting to mark entitlements as requestable, you can: - **Post-aggregation rule / workflow:** Set up a workflow (or rule, if supported in your tenant) that runs after aggregation and updates all entitlements where `requestable = false` to `true`. - **API automation:** Use the ISC REST API (or beta Graph API) to: - Search for entitlements with `requestable = false` - Update their metadata in bulk to set `requestable = true` Hope this helps!! ---
**Author:** ![tsandeepsTDC](https://avatars.discourse-cdn.com/v4/letter/t/bc79bd/32.png) [@tsandeepsTDC](https://developer.sailpoint.com/discuss/u/tsandeepsTDC)\ **Post date:** [June 20, 2025, 12:45am UTC](https://developer.sailpoint.com/discuss/t/how-to-make-entitlement-requestable-true-during-ad-group-aggregation/146364/3 "2025-06-20T00:45:51Z")
Ok.. Rule i can not use as its not straightforward deployment. Means we have only manual option to update this attribute either via UI or API. ---
**Author:** ![jesvin90](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/jesvin90/32/5301_2.png) [@jesvin90](https://developer.sailpoint.com/discuss/u/jesvin90)\ **Post date:** [June 20, 2025, 4:51am UTC](https://developer.sailpoint.com/discuss/t/how-to-make-entitlement-requestable-true-during-ad-group-aggregation/146364/4 "2025-06-20T04:51:56Z")
Hi @tsandeepsTDC, You can consider using a workflow to achieve this. 1. Setup a WF with a scheduled trigger, running after your aggregation timing. 2. Next step would be an HTTP action that can run a search query, fetching the entitlements marked as non-requestable. The search body would look something as below : ```auto { "indices": [ "entitlements" ], "query": { "fields": [ "name" ], "query": "source.name:\"ActiveDirectory\" AND requestable:false" }, "queryResultFilter": { "includes": [ "id", "name" ] } } ``` 1. Loop through each of these entitlements and then use an HTTP action inside the loop to patch each entitlement with [this](https://developer.sailpoint.com/docs/api/beta/patch-entitlement) API to mark the entitlements as requestable. ---
**Author:** ![davepeters](https://avatars.discourse-cdn.com/v4/letter/d/b38774/32.png) [@davepeters](https://developer.sailpoint.com/discuss/u/davepeters)\ **Post date:** [June 20, 2025, 5:56pm UTC](https://developer.sailpoint.com/discuss/t/how-to-make-entitlement-requestable-true-during-ad-group-aggregation/146364/5 "2025-06-20T17:56:21Z")
Be aware loops within workflow have a limit on how many items the can have. I believe it is 250 ---
**Author:** ![kanusha9](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/kanusha9/32/37041_2.png) [@kanusha9](https://developer.sailpoint.com/discuss/u/kanusha9)\ **Post date:** [June 21, 2025, 6:31am UTC](https://developer.sailpoint.com/discuss/t/how-to-make-entitlement-requestable-true-during-ad-group-aggregation/146364/6 "2025-06-21T06:31:50Z")
Use the below API to do the change. Body: { “op”: “replace”, “path”: “/requestable”, “value”: true } > **[patch-entitlement | SailPoint Developer Community](https://developer.sailpoint.com/docs/api/v2025/patch-entitlement)** > > \ **Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\ **Post date:** [August 20, 2025, 6:32am UTC](https://developer.sailpoint.com/discuss/t/how-to-make-entitlement-requestable-true-during-ad-group-aggregation/146364/7 "2025-08-20T06:32:23Z") This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.