Bug 41845 - Don't mix "allow" and "restrict" permissions
Summary: Don't mix "allow" and "restrict" permissions
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on: 20813
Blocks:
  Show dependency treegraph
 
Reported: 2026-02-13 16:52 UTC by Caroline Cyr La Rose
Modified: 2026-02-13 16:52 UTC (History)
2 users (show)

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Caroline Cyr La Rose 2026-02-13 16:52:20 UTC
In the current permissions, there's something that *really* bugs me : the mix of permissions that "allow" and permissions that "restrict".

I often create staff accounts as part of the set up we do for new clients and for non-superlibrarians catalogers, I always have to remember to check everything in cataloging EXCEPT that one annoying permission that restricts the subfields (SubfieldsToAllowForRestrictedEditing).

I was wondering if it was possible to take this into account when revamping the permissions.