Summary: | Patron category should regulate if account can have permissions | ||
---|---|---|---|
Product: | Koha | Reporter: | Christopher Brannon <cbrannon> |
Component: | Patrons | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | gmcharlt, kebliss, kyle.m.hall, sally.healey |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Christopher Brannon
2023-08-02 19:36:25 UTC
On further reflections, my second suggestion above should have its own preference setting to retain current behavior. - Create a pref, like ClearPermissionsAutomatically, where it defaults to Don't, but can be set to Do if you want permissions cleared automatically when changing patron to a category that doesn't allow permissions. +1 this is a great suggestion. Koha having the ability to clear permissions from an account when it moves from a 'permissions allowed category' into an ordinary patron category would be a huge help. Despite policies explaining otherwise, some staff members still believe that moving an ex-staff account to being an ordinary patron account revokes Koha access. I run a report to identify when this happens - but it would be very helpful if Koha could manage this automatically. |