https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35693
Lisette Scheer <lise...@bywatersolutions.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lise...@bywatersolutions.co
| |m
--- Comment #12 from Lisette Scheer <lise...@bywatersolutions.com> ---
I think this would be a good topic for the next development meeting.
Personally I think a role based access control (rbac) similar to the patron
permissions plugin we have with the option to set on the individual level if
there were niche permission sets would be great.
I also think something like
Object (item)
[]View
[]Edit
[]Delete
[]Add
[]View all branches
[]Edit all branches
[]Delete all branches
[]Add all branches
type granular permissions would be more what the bigger libraries we've talked
to would like to see.
You could set a role/persona with the permissions for example:
Circ staff
-View all items
-Edit items at my branch
and assign folks to a role/persona to grant those permissions, but another
example:
cataloger:
view all branches, edit items at my branch, delete items at my branch, add
items at my branch.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20813 Revamp user
permissions system (currently failed qa) has a number of bugs it depends on
that I filed last year as prerequisites to fixing the issues outlined on that
bug in it's current state.
--
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
Koha-bugs@lists.koha-community.org
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/
