Summary: | Privacy concerns in Notices | ||
---|---|---|---|
Product: | Koha | Reporter: | Joy Nelson <1joynelson> |
Component: | Notices | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | andrew, george, lisettepalouse+koha |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23660 | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Attachments: | Screenshot of possible permission |
Description
Joy Nelson
2020-02-25 17:41:32 UTC
If we do this, I hope we can do it as a separate system pref from intranetreadinghistory or as a staff permission or to possibly split checkout/hold history. Sometimes we use notices to track down various issues. I am thinking along similar lines as Lisette but, instead of a system preference, I'd rather see a permission similar to "updatecharges" or "reserveforothers" which both control two sub-level permissions. This way system administrators could control a staff's ability to manage content on the notices tab on a user-by-user basis rather than setting it system-wide for all users. I'm thinking a sub-level permission called "view_notice_content" that would allow anyone with that permission to view the content of the notices, a sub-level permission called "notices_remaining_permissions" that would allow staff to see the notices table and all of the other parts of that tab. And they could be grouped under a top-level permission called "notice_tab" that would turn the two sub-level permissions on and off. I'm attaching a screenshot to demonstrate what I'm thinking. Created attachment 99652 [details]
Screenshot of possible permission
|