Admin tools that control who can do what
Administration that holds up
Permissions are decided on the server, so hiding a button is never the whole security model.
Role matrix
Super Admin, Admin, Manager and User. Each role gets its own rights in every module, set from one clear table.
Deny by default
A missing permission row means no access, not full access. A role only reaches what you have clearly allowed it to use.
Audit logging
Every significant action is recorded with the person who did it and the module it touched. Filter the log by module and action.
Connection checks
One screen confirms that mail, licensing and payments are connected and working, so you spot a broken link before your customers do.
Change history
Settings, System, Logs, Change history shows who changed which record and when. You answer with a date, not a guess.
Sign-in alerts
After every sign-in, the person who signed in gets an alert by email or in the dashboard, with the device, browser and location.
How the admin tools check each request
Permission checks run in PHP on every request. The screens show those rules, but the rules are not the screens. A crafted request is refused the same way a hidden button would be.
This model is known as role-based access control. You give rights to a role once, and every person with that role gets them.
Four roles, set per module
PABAA comes with four fixed roles: Super Admin, Admin, Manager and User. You cannot add a fifth role, but you can set what each one may do in every module.
A Manager can work on tickets without seeing billing. An Admin can issue licences without changing security settings. Only a Super Admin can change permissions.
Logs that answer questions
The admin tools keep an audit log of each significant action, with the person and the module. You can filter it by module and action, and export it when a client asks.
Change history goes one step further. It records who changed a record and when, so you can answer with a date, not a guess.
Sign-in alerts tell people about each new sign-in to their account. A device or place they do not know is easy to spot.
One place to check connections
The admin tools also give you one screen that checks mail, licensing and payments. When something breaks, you see where before a customer tells you. See how roles fit with the rest of the PABAA feature list.
Who sees what on your team
Admin tools work best when each person has the role that fits their job. Give your support staff the Manager role, so they can work on tickets without seeing billing, and keep the Super Admin role for the few people who change permissions.
Frequently asked questions
Can I create custom roles?
No. The four roles are fixed, but you can set what each role may do in every module.
Are audit logs exportable?
Yes. You can export them and filter them by module and action.
Who can change permissions?
Only a Super Admin can change permissions.
Delegate without losing control
Give each person on your team the access they need, and no more.