LSU supports this request. We need to be able to allow roles to make updates to their opportunities, especially fund periods but not change the open and close dates. At least a date change restrictions

UWM would like to be able to add access to Site > Files > System Reports to a custom role, as they want some users to be able to run reports yet not have full system admin access.

Appstate supports this request. We have many adminsitrators that need to award scholarships but do not need access to change qualifications and portfolio information.

UW-Milwaukee is also interested in this functionality. We would like opportunity admins to be able to edit the details page of their conditional application for their school/college, but per BAM, this is only possible if we give them access to edit all portfolios. We would like to uncouple these permissions so they can be given access to edit conditional app details without being able to edit portfolios.

UW-Madison is still interested in this functionality. Since we are a decentralized campus, there are various degrees of access that individuals in scholarship need. Some individuals just need to see certain information but should not be able to adjust it. Other individuals need to see even less information due to data security.

Thanks Carrie. This is our institution���s highest priority request, so I have voted on it. It is almost a necessity at this point given the amount of resources needed to keep up with all of the changes our Opportunity Administrators are requesting of us, that could otherwise be eliminated if we were able to assign access to certain sections by role.

Jon-Michael Sima
Accounting Manager
Florida State University Foundation
850-644-1090
Forms & Resources
Web Reports

[FSU Foundation]

Please see similar request from Wisconsin-Madison below. It's a little different, but speaks to challenges around how permissions are set up in the system today:

"We've had issues with Opportunity Admins editing our System Template for reviewer groups, and we believe this should only be editable by System Admins"

I have just encountered a scenario where an opportunity administrator archived my three post-acceptance questions that applied to all of my opportunities.  I asked that the Archive option be removed or separated in the role permissions.  I also see where any question that is used by more than one scope would have an adverse affect if modified by an opportunity administrator, so I would like to see the permissions on roles be separated.  Right now, OA's cannot clone or set dates to open or close opportunities if you want to eliminate their ability to change or archive questions.

Please see another use case from UTA in the merged enhancement. Description below -

UTA would like the ability to restrict a custom role from editing questions separately from the rest of the permissions in that group. She specified that her opportunity administrators should be able to access and edit qualifications but should not have access to edit questions. Both of these are under the Apply-to, Auto-match, Flexible, and External Opportunity Permissions Details section so she has the option to give them View or Act permission on all of the items or none.

She had a scenario where an opportunity administrator changed an existing post-acceptance question which is required for ALL opportunities and this changed across the boards and caused major issues. She wants to remove access for the opportunity administrators to make changes to questions to avoid this from happening in the future.

Please see similar use case from ISU in the merged enhancement. Description below -

Our Foundations is concerned with opportunity administrators adjusting qualifications and then the qualifications not meeting with the Memorandum of Agreement and a student receiving an award they don't qualify for. With the permissions, if you want to turn off the qualifications for them, you turn off other things as well that we want them to have access too.