Bug 12793 - Breaking up IndependentBranches syspref to support finer staff permissions granularity
Summary: Breaking up IndependentBranches syspref to support finer staff permissions gr...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Architecture, internals, and plumbing (show other bugs)
Version: master
Hardware: All All
: P1 - high enhancement (vote)
Target Milestone: ---
Assignee: Galen Charlton
QA Contact: Testopia
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-20 16:22 UTC by Joel Sasse
Modified: 2019-01-22 19:55 UTC (History)
12 users (show)

See Also:
Change sponsored?: Seeking cosponsors
Patch complexity: ---
Bot Control: ---
When did the bot last check this:
Who signed the patch off:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joel Sasse 2014-08-20 16:22:21 UTC
Currently, if the IndependentBranches system preference is turned off, all staff regardless of library location have access to edit/delete items and patrons belonging to other libraries. Also, if you allow staff access to the calendar and notices & slips tools, they have access to all libraries' calendars and notices. There's too much potential for misuse here, either intentional or unintentional. 

Another serious permissions issue is the ability of any staff member to change their library location at will. Staff should not be able to change their library location unless explicitly given that permission. There's too much potential here for misuse as well, either intentional or unintentional.

Simply put, library staff should only have the permissions required to perform their job duties, nothing more. Koha currently gives staff far too many permissions, particularly with regard to items and settings belonging to other libraries.

The IndependentBranches syspref is far too restrictive to be useful for resource sharing consortia. It needs to be broken down for more granular control. For example, library staff in my consortium need to be able to edit patron info because many patrons use multiple libraries but they should not be able to edit items belonging to another library, including using the batch modification tool. 

My suggestions as a starting point would be to consider the following global system preferences under Administration:

Library staff may edit items belonging to other libraries (yes/no)
Library staff may edit patrons belonging to other libraries (yes/no)
Library staff may cancel holds of patrons belonging to other library (yes/no)
Library staff may change their location (yes/no)
Library staff may edit (only their own/all) notices
Library staff may edit (only their own/all) calendars

This assumes that the staff member is given the appropriate individual permissions under borowers, reserveforothers, editcatalogue and tools sections. I'm sure there are better ways to accomplish the permissions goals than the above; they are just suggestions to get the ball rolling.
Comment 1 Jeremy Evans 2014-09-17 12:44:03 UTC
I would support this.
We share our system with another organization, each having several branch sites.
Therefore we would like to be able to have the option to base the restrictions on library group. (we have already defined 2 library groups in Koha - one for each organization) that way we can manage patrons/bib records etc for the other sites within our own organization but not see anything for the other organization's sites.