https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32968
--- Comment #4 from Martin Renvoize <[email protected]> --- (In reply to Jonathan Druart from comment #3) > What are the real-life use cases we are trying to solve here? > > Maybe we are reproducing a wrong pattern with this approach (having all the > different permissions) and we should prefer something else. We could have > permissions that represent jobs in a library. I've long wanted to impliment a roles based access control system.. problem is I don't think a developer can define what permissions a role requires.. different libraries see different roles meaning different things. In my rebus:list days, we had very granular flags for each operation that could take place and then we had a role builder interface that allowed admins to create their roles and assign those granular permissions to them.. then end users were granted one or more roles on the system. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ 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/
