https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41845
David Cook <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from David Cook <[email protected]> --- (In reply to Caroline Cyr La Rose from comment #0) > 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. That's a good point. The way it's done currently drives me a little crazy. Going forward, I do think we need both "allow" and "deny" (or "restrict") permissions, but they need to be separated in a way the effective of the permission clear. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
