RBAC
RBAC stands for role-based access control: give each person exactly the access their job needs — no more. Permissions are set per area of the business, at the read, write or admin level, for one location or all of them.
Already have an account? Sign in
A new hire starts with the baseline
Access that follows the job, not the person who set it up.
Every page, button and API call in Pixelbase checks the same permissions, so what someone can do in one place is what they can do everywhere.
Presets for each job
Save a bundle like “Front desk” or “Bookkeeper” once, then grant a new hire their whole job in one step instead of a hundred checkboxes.
A baseline for everyone
Nominate one preset as your company’s floor. Everybody holds it, so nobody new is missed while their own permissions are sorted out.
Per-location access
A manager can run the customers and bookings at their own location without seeing the books for the others.
Read, write and admin
Seeing, changing and moderating other people’s work are separate grants, so a moderator doesn’t also get the write access they never asked for.
The same rules for agents and API keys
Tokens for the API, the CLI and connected AI agents carry these permissions too, and are never given more than the person who made them holds.
Admins you can see
Anyone who runs a part of your company is badged as an admin in your directory, so who can change what is never a guess.