More Granular permissions for Libki

[sekjal]

Right now, Libki has 2 levels of admin permissions: admin, and superadmin, with the both allowed to access the administration interface, but only the latter allowed to edit Settings and view Logs. For deployments to institutions with few staff, this is acceptable, but larger institutions may need more granular permissions. Below is a list of explicitly defined permissions we could add to Libki. Please reply with ideas for further permissions.

Users:

• create regular user
• create guest user
• edit user (including toggling Troublemaker, enable/disable)
• delete user
• add manual funds to a user account

Clients:

• manage client (shutdown, restart, drop, etc)
• delete client

Sessions:

• End session
• modify session time

Reservations:

• make a reservation
• edit a reservation
• cancel a reservation

Print Jobs:

• view someone else's print file
• edit someone else's print job
• release a print job
• cancel a print job

Settings:

• edit system Settings
• create a Location
• edit a Location
• edit Location hours/exceptions
• delete a Location
• view history and statistics
• view logs

[cbrladmin]

@sekjal I think one of most important features needed is, admin users need to have filtered access. Currently, admin users can access any site. But filtering access to only certain location (sessions and clients) would be very beneficial.