Bug 18787 - Create permission profiles for staff users
Summary: Create permission profiles for staff users
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement with 6 votes (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
: 6223 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-06-12 14:19 UTC by Séverine Queune
Modified: 2024-02-01 12:17 UTC (History)
9 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
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 Séverine Queune 2017-06-12 14:19:34 UTC
It would very useful if we could define different permission profils, depending on the library uses, to prefill permissions.

For example, in our site, we could have :
  - a "catalog profil" to edit records and items
  - a "subscription profil" because there is a team which works specifically on periodical publications
  - a "circulation profil" because some of us don't work directly with patrons so they don't need to access to the Patron and Circulation module (but they could borrow books for themselves)
  - a "team manager profil" because they have permission to see acquisition budget for all their team
  - etc.

It would be an easier way to define permissions for a new staff user and a way to be sure all the accounts are identically set.
Comment 1 Katrin Fischer 2018-05-17 22:49:30 UTC
*** Bug 6223 has been marked as a duplicate of this bug. ***
Comment 2 Séverine Queune 2021-03-09 07:14:11 UTC
Just discovered this plugin, but not tested yet.
https://github.com/bywatersolutions/koha-plugin-batch-permissions-modifier
Comment 3 Alexander Wagner 2023-08-22 14:42:57 UTC
Indeed it would be nice to have something along the lines of unix-groups that assign certain rights. E.g. I could define what cataloguers can do or the ILL staff and then assign people to be cataloguer and/or ILL staff easily. Indeed, I spent some time to fiddle out that this seems not to exist (yet). In view of Bug 6223 also the term `roles` comes to mind.

The https://github.com/bywatersolutions/koha-plugin-batch-permissions-modifier plugin Séverine mentioned goes in this direction indeed and populates permissions from a template user to all users on a given patron list. It works pretty well as far as I tested it, just in "auto" mode it seems not always to trigger. (IOW I had to run it manually from time to time to propagate permissions.) I'll have to check what happens if some user shows up in two lists, though. It doesn't look like this is meant to be.

Configuration might get a bit ugly as one has to add template patrons and lists to handle all set up by bare numbers.
Comment 4 Marie-Luce Laflamme 2024-01-31 23:08:05 UTC
+1. This is a great idea!
Comment 5 Alexander Wagner 2024-02-01 12:17:48 UTC
Diving into the mentioned plugin I found indeed that it assumes each patron gains only one set of permissions (iow you can not be in more than one group). For this reason I came up with a small perl script than will handle permission setup for j2k. This script basically reads an input file giving the name of the role someone should have and her cardnumber. It will then create a patron list for the roles, add patrons to the list (for easy reference) and add permissions accordingly.

This script could need a bit of improvement for general use. E.g. an immediate thing would be to move the hard coded hash for permissions to some source read in, and probably for koha purists the idea to have files around that implement the functions are not that common. (It's just easy for me to handle those files in git within j2k.)

But maybe one could build upon it.