More Granular Permissions for Creating Report Templates and Viewing Output

Bug #1948985 reported by Jessica Woolford
54
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
Revision history for this message
Lindsay Stratton (lstratton) wrote :

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.

Revision history for this message
Andrea Neiman (aneiman) wrote :

Reports Security, bug 2043132, attempts to address some of this.

Revision history for this message
Elizabeth Davis (elidavis) wrote :

To add to this-it would be helpful if staff can be limited to running reports only on working org unit.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.