# Configuring Workflow to Remove all OOTB Entitlements in IdentityNow **URL:** \ **Category:** SHF Discussion and Questions\ **Tags:** workflows, sailpoint-identity-security\ **Created:** [July 3, 2024, 5:23am UTC](https://developer.sailpoint.com/discuss/t/configuring-workflow-to-remove-all-ootb-entitlements-in-identitynow/70752 "2024-07-03T05:23:22Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![mostafa\_helmy](https://avatars.discourse-cdn.com/v4/letter/m/439d5e/32.png) [@mostafa\_helmy](https://developer.sailpoint.com/discuss/u/mostafa_helmy)\ **Post date:** [July 8, 2024, 10:46am UTC](https://developer.sailpoint.com/discuss/t/configuring-workflow-to-remove-all-ootb-entitlements-in-identitynow/70752/6 "2024-07-08T10:46:27Z")
At a very highlevel, you can use a workflow to remove access outside of birthright auto-mapped roles (as you already referenced here: [ Workflow to Remove ALL Leavers’ Standing Access ](https://developer.sailpoint.com/discuss/t/workflow-to-remove-all-leavers-standing-access/13025)) The challenge will be in trying to find out which out-of-birthright-access has been granted via approved access requests. I am not aware of any effective or easy way - within workflows at least - to find out whether certain access was provided through access requests. Hence, the best approach might be to simply use workflows to generate a Mover certification campaign and assign it to the new manager to decide. Other SailPoint ISC components, such as the AI recommendations engine, should highlight any out-of-normal access items the mover has to the reviewer so they can make better decisions. --- _[View the full topic](https://developer.sailpoint.com/discuss/t/configuring-workflow-to-remove-all-ootb-entitlements-in-identitynow/70752)._