The driver web portal

The driver web portal is a separate part of the site, at /driver, that drivers sign in to with the same account they use on the phone. It is not a cut-down version of the admin dashboard and it is not a browser copy of the app: it is a place for a driver at a desk to look things up, keep their own details current, and clock on.

It is off unless your organisation turns it on, and only driver accounts can reach it. An administrator opening the same URL is refused — the portal is scoped to the driver user type, not to a permission.

Two live cues sit in the navigation: a pulsing green dot on Shifts while the driver is on shift, and a dot on Messages when something is unread. The bell in the top bar is not one of them — it is there for layout, and is not wired to a notification source.

The trip detail page is the clearest example. A driver can open their own trip and inspect every tab of it — stops, tasks, cargo, documents, locations, events and exceptions — but there is no way to change its state, no add, edit or delete, and no route optimisation. The screens are the same ones the office uses, with every mutating control removed.

Tasks draw the line more finely. A standalone task — one with no trip behind it — can be started, skipped, failed or completed from the browser, with an outcome recorded where the transition needs one. A task attached to a trip stop cannot, and the panel says so plainly: complete this on the mobile app.

The Profile page splits into what the driver owns and what the organisation owns. They can edit first and last name, phone, address, and the emergency contact name and phone.

Licence number, class and expiry, years of experience, hire date, background check and medical exam expiry are shown but not editable, and neither are the account fields — status, account status, created, updated, last login. These are compliance records and administrative state; a person being able to edit their own licence expiry would make the compliance score worthless.