2018-09-06 Resource Access Meeting Notes

• Note-taker - Joanne Leary

The Requests Sub-group has defined the following permissions needed for requests:

• View requests
• Edit & Cancel requests
• Create requests
• All permissions

The breakdown of what would be allowed can be seen on the Requests tab of this spreadsheet:

https://docs.google.com/spreadsheets/d/1IJnlWvi4k-wFatDNimx9fQ375evHSIIxtGMookHvs-I/edit#gid=525257038

Two things Tania would like signoff on (besides the general concept) are:

1. Any user who can access requests is allowed to add a note - the reasoning is that if they are allowed to see a request, they should be allowed to add a note to it to annotate the request with any info that might be needed by another staff person who may have higher permissions and can act on a note
   RESOLUTION:  Anyone who views, adds, updates, or cancels a request should be able to add a note for internal staff use.
2. Edit and cancel permissions can be tied to each other - right now in the back end they are using the same function.  We could separate them but it would facilitate quicker development if the two functions don't need to be separately assigned.  The subgroup thought this would be OK - does anyone know of a compelling reason to separate them?

RESOLUTION:  This is the first time we are deciding on permissions for Resource Access.  We want the RA permissions to be consistent across all features–we want each permission to be separate:  Edit and Cancel should not be together.  Also, should not have an All permission.  Instead, institutions will be combining permissions to make permission groups for various types of users.  For example, a Requests Staff Supervisor roles would have Create, Edit, and Cancel combined into a group.   There may be a Requests Student Supervisor role that can Create and Edit a Request but not Cancel it.  Anya mentioned Cate's Permissions PowerPoint that we should look at.  We will review this and then reconsider Tania's question.