The role catalogue
Each role covers one area of responsibility. If someone needs two areas, give them two roles — see Common role combinations.
| Role | For whom | What it covers |
|---|---|---|
admin |
Customer administrator | Everything except managing role definitions. The highest role assigned to customer employees |
hub_manager |
Operations manager | Full hub — assign, force delivery, cancel, modify ETA, incidents, alarms — plus store configuration, pause delivery, metrics and archived alarms |
hub_operator |
Hub shift operator | Basic hub operations, without the critical actions. View stores and metrics |
branch_manager |
Store manager | Their own store: view orders, modify ETA, incidents, alarms, driver alerts, pause delivery, store configuration |
branch_viewer |
Read-only store access | Viewing store configuration only. A support role, designed to be combined with others |
dispatcher_manager |
Logistics technician | Dispatcher execution, scheduler, store configuration, pause delivery, delivery zones, third-party carriers, metrics |
report_viewer |
Management and analysts | Reports, metrics, view stores |
polygon_manager |
Delivery zone configuration | Delivery zones, view stores |
cms_editor |
Content editor | Complaints tree, resources, images |
employee_manager |
HR and staff configuration | Employees and own drivers, plus role assignments, scope and exceptions |
third_party_manager |
External fleet configuration | External carrier configuration, at brand level |
alarms_config_manager |
Alarm threshold configuration | Alarm thresholds for orders, drivers and stores, across the whole chain |
Two roles you won't assign
super_admin is a PizzaGest internal technical role. It has full access and bypasses every check, and is never assigned to customer employees.
admin is the customer-side equivalent for day-to-day purposes: the same operational reach, except that individual denies still apply to it and it cannot change role definitions.
How permissions add up
Roles are built from a catalogue of atomic permissions — currently more than fifty, each covering one specific action such as "assign a driver" or "export metrics".
A role is a named subset of that catalogue. When an employee holds several roles, their permissions are combined, without duplicates. Nothing is subtracted by adding a role.
Permission counts per role change as new modules ship. Rather than memorising a number, check what a role actually grants in Access by section, or open the role in the Role catalogue screen.
Recently added modules
Chatbot configuration, External API management, the Voice agent, Promotional codes and Voucher codes are currently reachable by admin only. Whether they get a dedicated role, or are folded into existing ones, will be decided based on operational need.
If one of these needs to reach a non-admin employee before then, an individual exception is the intended route — see Individual permission exceptions.