More Granular Permissions for Creating Report Templates and Viewing Output
Bug #1948985 reported by
Jessica Woolford
This bug affects 11 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
This was discussed at the Reports Interest Group meeting at the 2021 conference.
Currently, the permissions that allow the creations of templates and viewing of report output are very broad. It would be desirable to limit the types of reports staff could create and view based on their role in the library. Not all staff need or should have access to patron data, for example.
tags: |
added: permissions removed: permission |
Changed in evergreen: | |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
tags: | removed: wishlist |
To post a comment you must log in.
To add to this - it would be desirable to be able to differentiate between cloning templates and creating new templates.
Case in point: we allow staff users to create their own templates. Yesterday, reports run from an ill-formed staff template jammed up the entire reporter, preventing all other users' reports from running until the stuck reports were cleared.