Currently the message template that are dependent on scope say they are sent to "relevant Opportunity Administrators". This is incomplete in that the messages are also sent to System Administrators with the scope. The language should reflect that.

I don't know functionally if this would be possible, but The University of Texas at Arlington would like to be able to have blind reference reviews. Their committee members may know the professors that submitted the reference and it may bias their...

We have some external opportunities that we list that do not have websites for their awards. We just add a link to a scanned application in the description that students can fill out and send in to the organization. The deadline date is not visibl...

They would like their users to not be able to edit the description, yet still be able to edit questions and quals. "This is a field that only our CSU Foundation folks (system administrators) should be able to update. We enter the criteria for o...

I would like the "scope" to change immediately instead of waiting for the person to log-in. Our scholarship committees change every year and there is no way for me to check it has been updated unless I go into every user. When I select users by sc...

Customers would like some higher level of control over permissions, e.g., who has the ability to edit opportunities.

SAs want to be able to order the way profiles appear on /donors to put more high profile ones toward the top.

It can be difficult for OAs to visually distinguish qualification groups, especially if there are several similar ones in a row. If we did a simple enumeration, it would help them tell them apart.