Permissions matrix
A one-page grid of which role can do what in Klu.
Overview
Klu gates features by role — OWNER / HEAD_MANAGER / MANAGER / STAFF. This page is the full grid of who can do what.
Role matrix
| Action | OWNER | HEAD_MANAGER | MANAGER | STAFF |
|---|---|---|---|---|
| View all pages | Y | Y | Y | Y (branch-only) |
| Create product | Y | Y | Y | N |
| Delete product | Y | N | N | N |
| Manage price profiles | Y | Y | Y | N |
| Invite team member | Y | Y (MANAGER only) | N | N |
| Manage roles | Y | Y (MANAGER only) | N | N |
| Remove team member | Y | Y (MANAGER only) | N | N |
| Manage branches | Y | N | N | N |
| Approve purchase request | Y | Y | Y | N |
| Create transfer order | Y | Y | Y | N |
| Move stock | Y | Y | Y | Y |
| Record waste | Y | Y | Y | Y |
| Create / edit promotion | Y | Y | Y | N |
| Manage staff | Y | Y | N | N |
| View all analytics tabs | Y | Y | Y | N |
| Upgrade subscription | Y | N | N | N |
| Delete supplier | Y | N | N | N |
| Revert a sale | Y | Y | Y | N |
Tips & gotchas
- STAFF sees only their assigned branch — the branch selector is effectively locked.
- HEAD_MANAGER can only manage users below them (MANAGER level). They can't touch other Head Managers.
- OWNER is unique per organization — transferring ownership is done via support, not from the UI.
- Permissions are enforced in multiple layers — even if the UI allows an action, the system will prevent it if you lack permission.