Who do you give supervisor rights to?

@Jolynn Uyehara
Db view Admin > Security and select the group that has the user in. Then Records, click options. Under constituent record types, in the privileges pane scroll almost half way down.

@Jolynn Uyehara:

@Dariel Dixon I hate to admit this, but everyone has supervisor rights. ? At least in the development office. I know it's a bad idea and I am working on tightening up security and limiting access for many. I welcome any suggestions you have. Thank you!

To solve the issue you mentioned for your fundraiser, @JoAnn Strommen is right about where to access that information, but really all you need to do is mark the fundraiser as a solicitor on their RE constituent record. In database view that check box is on the bio1 tab. In webview it is under the “Mark as…” drop down.

Overall, I would try to categorize the office staff based on what they need to do in the database. For example, everyone might need to view gifts, but only a handful will need the ability to add or edit them. Sometimes what I do is change access to view only and then see if I get a request from anyone. If I don't then I have tightened up access and if I do, then I can better understand the various roles and processes happening in the office.

@Jolynn Uyehara When I came aboard our organization, the first thing I do, was take supervisor's rights away from anyone who had them with the exception of two folks working under me. Other folks, I took away their rights where they were able to delete items, etc. I came aboard and just told everyone this is how the new era will be and they accepted that. Sometimes you have to just put your foot down for the sake of the database and the organization.

@Jolynn Uyehara
Sorry, I think I thought you were talking about assigning things like actions to themselves, but it sounds like you are talking about assigning themselves as a fundraiser in which case, @JoAnn Strommen has your answer.

I've seen a lot of responses where people have mentioned that they have just removed admin rights from people that didn't need them or should not have had them to begin with. While I think this is a cool concept, I'd be remiss to not mention that this is not something every environment will allow. Please recognize the work environment and culture. Not all DB admins will have the backing of management, and sometimes they can be a hinderance to progress instead of being helpful. I hope you can devise a plan that is beneficial to all. Be strategic! There is a way that this can be done that reduces conflict. That said I wish you good luck and Godspeed with this change.