Date
...
Functional Area | Product Owner | Planned Release (if known) | Decision Reached | Reasoning | Link to supporting materials | Comments |
|---|---|---|---|---|---|---|
| e.g. loans, fees/fines | Name | e.g. Q4 2018, Q1 2019 | Clearly stated decision |
| e.g. mock-up, JIRA issue | |
Notes:
Permission management - Erin Nettifee - New permissions management proposal from App Interaction
https://docs.google.com/document/d/1QaKLtxQE_bgg3Hq2r8OtkGhpmVyIj2nbCvcIkdqXcXw/edit?usp=sharing
In December/January, a number of issues that implementers were having with permissions management bubbled up. Investigation was deleted to App Interaction, which created this proposal for a new staff permissions user interface. New functionality in the proposal includes ability to assign or remove users to/from a permission or permission set and more permissions metadata in the UI. Could be implemented within Settings or as a new app.
Erin = bringing it to RA SIG today for feedback.
Question about whether or not proposal includes ability to assign multiple users to a permissions set at one time. Per Erin, this *is* within scope, and proposal will be revised to make this more clear.
Can .CSV export feature be included? Answer: yes!
Discussion about whether it would be preferable to implement within Settings or as a new app in the short and long runs. Argument for settings = it’s a systems configuration; argument for app = especially at larger institutions, permissions management isn’t always a systems administration task anymore and an app would make this easier.
No PO has been identified for this yet, so it’s unclear when it will move forward.