Remove roles automatically for withdrawn staff
When staff leave, currently I have to go see which roles they are assigned and remove each one (some through Employment, some through Manage Roles). The withdrawal process should automatically remove all their roles (platform manager, activity leader, content editor, etc).
Additionally, when I withdraw the employee via Core > Users/Access >Profile, they are assigned "Past" roles but don't always lose the current roles. For example, I withdrew someone who was an Advisor, and now she has BOTH the Advisor role and the Past Advisor role. This is inconsistent, and I have to try to avoid it by first editing their employment and removing all the roles, saving, then going back and withdrawing them. This is a bug and needs to be fixed.
-
Oona McKnight
- Apr 12 2017
- Under consideration
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +35
Related ideas
Continue to keep the history, please. It helps with giving roles to new hires.
If an employee is no longer with the school, they should also be withdrawn from their groups - or have that option in the core space where we "unemploy" the person. I've had several instances where employees who are also parents receive notices from groups they shouldn't be a part of, and in those instances they were admin staff who had to be in every community group so it was tedious to go through and remove them from their leadership spot and their manually added spot
Past employees still receive Admissions Committee, Monitoring Teams and Donation notifications even after their employment is disabled AND their roles are removed. There is not report or a way to find these people either. This is a HUGE confidentiality issue that is an inexcusable oversight by Blackbaud that was reported in 2017.
We are experiencing this issue and several confidential messages have been sent outside the organization as a result, with no idea this was even an issue, let alone a needle in a haystack. Unexcusable, this needs to be fixed with a high priority.
Not just roles, they should be removed from all groups as well.
I was referred to this idea by Support. We found that when a user moves from Advisor to Past Advisor and not manually removed from advisories, that user is still receiving infraction notices/details for the advisees in those groups. This is not intuitive since one thinks rights are based on roles and the user no longer has the Advisor role. This is a Parent who is still active with the school, so the account is still active in Blackbaud, as it should be. My scenario seems a little different than this idea but similar. Just doesn't seem this is working correctly but Support says it is.
Yes, and an additional function to remove them from all groups would be helpful as well!
This should be a top level importance for security!
This is a major security flaw. No one told us we needed to remove the manager roles from withdrawn staff. Not even my instructors at blackbaud university said I had to do that.
I only found out about this because a past staff member brought it up. I had to spend hours going back to every past staff member to remove their roles.
There should also be at least an option to withdraw them from the groups they belong to!