Search Results

Audience: Platform administrators who decide who can do what in the console. You need: the Assignments and Scope sections, available to admin and employee_manager. Access in the console is built on two independent ideas. Keeping them apart is the key to the ...

Every employee has a single scope, which controls what data is visible to them everywhere in the console. The two modes Mode What it means Customer Full access to all data across the entire chain Explicit Access restricted to specific brands, stores and/or sou...

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 cus...

The full grid of what each role reaches. Legend: 👁 read-only · ✏️ read and write · — no access. All access shown here is then filtered by the employee's scope — see Scope: what data an employee can see. Section admin hub_manager hub_operator dispatcher_manager...

Because an employee can hold several roles and all of them share one scope, most real profiles are built by combining two or three roles rather than looking for a perfect single match. Real profile Roles Scope Operations manager who also views reports hub_mana...

Four behaviours explain almost every "why can this person see that?" question. Roles are additive An employee with hub_manager + report_viewer can operate the hub and view reports. Neither role restricts the other, and the order you assign them in makes no d...

The console manages roles, assignments, scopes and individual exceptions through four sections. Section What it lets you do Required permissions Role catalogue View, create, edit and delete role definitions — their name and the permissions they include roles:r...

You need: employees:read and employees:write — held by admin and employee_manager. Scope is set once per employee and applies to everything they do. See Scope: what data an employee can see for the model; this page is the task. Before you start Decide whic...

You need: employees:read and employees:write — held by admin and employee_manager. An exception grants or denies one specific permission to one specific employee, on top of whatever their roles say. Use it when a person matches an existing role in every re...

Creating or editing a role definition is restricted to PizzaGest's technical team. As a customer administrator you assign existing roles, set scope and manage exceptions — but the role catalogue itself goes through a request. This page explains why, and how to...

Audience: hub operators, shift managers and operations managers working the live order board. You need: Hub — orders and status at minimum. Individual actions each need their own permission, listed below. The Hub is the live operational view of orders in fligh...

You need: Hub — orders and status. The order board is the working list of orders currently in play across the stores in your scope. Filtering by store The main filter is stores: pick one, several, or leave it open for everything within your scope. This is the ...

You need: Hub — orders and status for the detail view; Hub — pickup code to see the pickup code, which is a separate permission. The detail view is the single screen worth screenshotting when you report a problem — it carries the timestamps and the current ass...

You need: Hub — assign to assign and to see available drivers. Unassigning is a separate permission, Hub — unassign, typically held only by hub_manager. Seeing who is available Open the order and ask for available drivers. The list is built for that specific ...

You need: Hub — modify ETA. Held by hub_manager and branch_manager. The promised time is what the customer was told, and what the system measures lateness against. Changing it is the right move when the original promise is no longer achievable and the custom...

You need: Hub — incidents to record one. Reading the incident catalogue needs only Hub — orders and status. An incident records what went wrong on a specific order, so it can be explained later and counted across orders. The incident catalogue Incidents are ch...