# The Hub: what it is and who can do what

> **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 flight. Where the dispatcher decides automatically, the Hub is where a person intervenes: assigning a driver by hand, changing a promised time, logging an incident, or — rarely — forcing an order closed.

## What the Hub is for

The dispatcher already assigns most orders on its own, every cycle. You open the Hub when something needs a human: an order the algorithm couldn't place, a customer calling about an ETA, a driver who never picked up, a store whose alarms are firing.

If you want to understand *why* an order was assigned the way it was, that is the dispatcher's logic rather than the Hub's — see [What the dispatcher does](/books/console-yF7/page/what-the-dispatcher-does).

## What each action needs

Access is granular on purpose. Holding the Hub view does not imply holding the critical actions.

| Action | Permission | Who typically has it |
|---|---|---|
| See orders and status | *Hub — orders and status* | `hub_operator` and above |
| See an order's pickup code | *Hub — pickup code* | Kept separate from assigning, deliberately |
| Assign a driver | *Hub — assign* | `hub_operator` and above |
| Unassign a driver | *Hub — unassign* | `hub_manager` |
| Change the promised time | *Hub — modify ETA* | `hub_manager`, `branch_manager` |
| Log an incident | *Hub — incidents* | `hub_manager`, `branch_manager` |
| Cancel an order | *Hub — cancel* | `hub_manager` |
| Force delivery | *Hub — force delivery* | `hub_manager` |
| View driver alerts | *Hub — driver alerts* | `hub_operator` and above |
| View branch alarms | *Hub — branch alarms* | `hub_operator` and above |
| Archive alarms | *Hub — archive alarms* | `hub_manager` |
| Change alarm thresholds | *Alarm settings — edit* | `alarms_config_manager` |

A `hub_operator` deliberately has the everyday actions but **not** force delivery, cancel or ETA changes. See [Access by section](/books/console-yF7/page/access-by-section) for the full grid.

> The pickup code is a separate permission from assigning, even though in practice the same people usually hold both. Keeping them apart means reading a pickup code never has to be bundled with the ability to move orders between drivers.

## The pages in this chapter

| Task | Page |
|---|---|
| Find an order, understand the board | [The order board](/books/console-yF7/page/the-order-board) |
| Look at one order in detail | [Order details and pickup code](/books/console-yF7/page/order-details-and-pickup-code) |
| Put an order on a driver, or take it off | [Assigning and unassigning a driver](/books/console-yF7/page/assigning-and-unassigning-a-driver) |
| Change what the customer was promised | [Changing the promised time](/books/console-yF7/page/changing-the-promised-time) |
| Record what went wrong | [Logging an incident](/books/console-yF7/page/logging-an-incident) |
| Stop an order entirely | [Cancelling an order](/books/console-yF7/page/cancelling-an-order) |
| Close an order the system couldn't close | [Forcing a delivery](/books/console-yF7/page/forcing-a-delivery) |
| See stores and driver alerts | [Stores and driver alerts](/books/console-yF7/page/stores-and-driver-alerts) |
| See and act on store alarms | [Branch alarms](/books/console-yF7/page/branch-alarms) |
| Tune when alarms fire | [Alarm settings](/books/console-yF7/page/alarm-settings) |
| Review alarms already dealt with | [Archived alarms](/books/console-yF7/page/archived-alarms) |

## What you can and can't see

Everything in the Hub is filtered by your scope. A `branch_manager` sees their own store's orders; a chain-wide role sees all of them. Two colleagues looking at the same board can legitimately see different orders — see [How scope works in practice](/books/console-yF7/page/how-scope-works-in-practice).