# RapidSetup Leaver Negative Role Assignment **URL:** \ **Category:** IIQ Discussion and Questions\ **Created:** [February 28, 2022, 9:30pm UTC](https://developer.sailpoint.com/discuss/t/rapidsetup-leaver-negative-role-assignment/3197 "2022-02-28T21:30:07Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![patrickboston](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/patrickboston/32/5876_2.png) [@patrickboston](https://developer.sailpoint.com/discuss/u/patrickboston)\ **Post date:** [February 28, 2022, 9:30pm UTC](https://developer.sailpoint.com/discuss/t/rapidsetup-leaver-negative-role-assignment/3197/1 "2022-02-28T21:30:08Z")
I put this on Compass and opened a ticket for a client but haven’t received a response yet, so trying here as well. We have the RapidSetup Leaver configured to remove all assigned roles upon termination. This sets the `negative="true"` flag on all RoleAssignments associated with an identity (RapidSetup and Business role types). The issue I am running in to is upon rehire (which is a non-rapidsetup workflow we developed since rapidsetup doesn’t have it’s own rehire event), the negative flag is sticking around on RoleAssignments which are tied to Business roles. RapidSetup Birthright roles that are to be re-assigned back during that rehire event are successfully given back to the identity with no negative flag, but the Business roles that someone should have re-assigned via an identity refresh with refresh roles/provision assignments is not happening because the negative flag is not removed. Is this expected behavior? Is there something specific that we should be doing during rehire to make sure the negative flag is not retained on these business RoleAssignments? Ideally, the RapidSetup leaver would just remove the RoleAssignments rather than setting the negative flag and we would not be in this situation at all. This is on 8.1p1. ---
**Author:** ![paulo\_urcid](https://avatars.discourse-cdn.com/v4/letter/p/848f3c/32.png) [@paulo\_urcid](https://developer.sailpoint.com/discuss/u/paulo_urcid)\ **Post date:** [February 28, 2022, 10:50pm UTC](https://developer.sailpoint.com/discuss/t/rapidsetup-leaver-negative-role-assignment/3197/2 "2022-02-28T22:50:34Z")
I believe it is not expected behavior (might be a bug). I think there was even a similar bug reported for the Accelerator Pack, and the workaround was to use some custom Rule to clear out those negative RoleAssignments. See the latest Accelerator Pack release notes and look for IIQSR-446: [https://community.sailpoint.com/t5/Accelerator-Pack/Accelerator-Pack-8-2p1/ta-p/202615](https://community.sailpoint.com/t5/Accelerator-Pack/Accelerator-Pack-8-2p1/ta-p/202615) ---
**Author:** ![patrickboston](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/patrickboston/32/5876_2.png) [@patrickboston](https://developer.sailpoint.com/discuss/u/patrickboston)\ **Post date:** [February 28, 2022, 11:52pm UTC](https://developer.sailpoint.com/discuss/t/rapidsetup-leaver-negative-role-assignment/3197/3 "2022-02-28T23:52:28Z")
Thanks Paulo. This is exactly the response I was looking for. Unfortunately, I could not get this response in a support ticket 🙂 Rather than fixing this during rehire, I just added a step in the RapidSetup Leaver workflow to set the `negativeAssignment` flag to `false` for any AttributeRequests for assignedRoles. This way, the provisioner just removes the RoleAssignment rather than leaving it with the negative flag. ---
**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\ **Post date:** [July 19, 2023, 2:25pm UTC](https://developer.sailpoint.com/discuss/t/rapidsetup-leaver-negative-role-assignment/3197/4 "2023-07-19T14:25:31Z")