Libraries in a consortium often rely on consortium administrators for support in managing permissions and trouble shooting issues with the ability of users in the system to perform their critical functions
- Complex systems could include large numbers of users as well as hundreds of roles and functions that users must perform
- Students and intern staff are relatively transient and the adjustment of permission assignments for these users is a frequent task
Use Cases & Requirements:
User that configures permissions sets is the person who assigns permissions to user
|Multiple Admins create permission sets and assign permissions to staff. Staff may or may not be assigning and unassigning users. Student perms change so often they try to distribute the responsibility|
|1 Admin configures permission sets and generally assign staff to permission sets. Staff that manage the student works will actually assign permissions to their student workers|
User needs to see the granular perms of a specific user on the user record for troubleshooting.
Generally a security vulnerability to display user permissions to anyone who can see staff users (User could target other users based on their permissions linger at their workstation etc.)
Using nested permission sets. Creating sets based on function and then adding those to role based permissions sets. So there is a hierarchy and organizational changes are easier to manage. Functional permissions are generally left unchanged.
When identifying why user 1 can not do what user 2 can do we compare their specific permissions or permissions sets.
|When new permissions are added functional permissions sets are updated. Admins then compare permissions sets to verify all necessary functions are included|
Work Breakdown Structure: