You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
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:
Clients:
Sessions:
Reservations:
Print Jobs:
Settings:
Beta Was this translation helpful? Give feedback.
All reactions