Cannot Edit Permissions within Permission Group
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Undecided
|
Unassigned | ||
3.8 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Version 3.4, 3.5 +
Within the new Angular version of the Permission Group interface (Administration -> Server Administration -> Permission Groups), there is not a way to edit the values of the group's inherited permissions.
For example, (using the out-of-the-box permission group structure) if the System Administrator inherits the Copy_Holds rule from the Staff permission group, Staff only has this permission at branch level and not grantable. If the System Administrator wants to have this ability at the system/consortium level and grantable, there is not a way to re-scope the depth of a permission or to select/deselect grantable.
The current option is to add the same permission to the user group that they already inherited and then scope / set grantable, etc. This leads to duplication of permissions within the interface (and not entirely clear which permission value will take precedence).
Image attached.
Changed in evergreen: | |
status: | New → Confirmed |
Changed in evergreen: | |
assignee: | nobody → Bill Erickson (berick) |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
Hi Erica, I have some work flow questions
1. I can imagine it being useful to see that an inherited permission exists and is superseded by a "closer" permission. What if we tagged the inherited permission as "overridden" in the UI to make it clear it's not active for the selected group?
2. As for creating the overriding permission, the concern is that having to add a new permission as opposed to modifying the existing inherited permission is not intuitive?