Notification center
The notification center collects everything happening across your fleet that needs your attention — from expiring documents to a message from dispatch — in one place. Every event carries a type, and the type decides who receives it by default and on which channels; you can override that routing per organization (see Alert rules).
Who it's for
Every signed-in user with an active membership has their own notification center — you only ever see notifications addressed to you. Which event types reach you depends on your roles (see Roles & permissions).
The bell and the list
The bell in the console's top bar shows your unread count and opens a panel with the latest entries on click. The full list (with an all/unread filter) lives on its own notification-center page. Opening a notification marks it read and takes you to the related record — a vehicle's detail page, a work order, or a dispatch message thread, for example; you can also mark a single item, or every item, read without opening it.
Where the browser supports it (an installed PWA, some desktop browsers), your unread count is also mirrored onto the app's icon as a badge — this is an optional, feature-detected enhancement that never blocks the console where it isn't available.
Event types and default routing
The table below lists all 19 event types the platform can raise as notifications, what triggers each one, and who receives it by default — unless the organization has configured its own alert rule for that type, which overrides this default routing.
| Event | What triggers it | Default recipient |
|---|---|---|
| Driver credential expiring | A driver credential (e.g. a license or certificate) reaches its expiry threshold | Compliance officer, safety manager, fleet manager |
| Document expiring | A document in the fleet's vault (e.g. an insurance policy or vehicle registration) reaches its expiry threshold | Fleet manager, organization administrator |
| Fuel fraud flag raised | A reconciliation rule or a manual flag marked a fuel transaction as suspicious | Finance controller |
| Geofence breached | A vehicle entered, exited, or dwelt too long inside a marked geofence | Dispatcher, fleet manager |
| Hours-of-service risk | A driver's HOS clocks show an active or imminent limit breach | Compliance officer, safety manager, and the driver themself |
| Maintenance due | A vehicle's preventive-maintenance schedule became due | Maintenance manager, fleet manager |
| Missing daily DVIR | A vehicle subject to a mandatory daily inspection (DVIR) has no record for the day | Compliance officer, safety manager |
| Device stopped reporting | A linked telematics device stopped sending data past the allowed stale window | Fleet manager, maintenance manager |
| Safety event confirmed | A safety event was confirmed on review and the driver's score changed | Safety manager, fleet manager, and the driver themself |
| New dispatch assignment | A dispatcher assigned a route or job to a driver | The assigned driver only |
| Message from dispatch | A dispatcher sent the driver a message in the dispatch thread | The addressed driver only |
| Driving/rest-time infringement | An active driving/rest-time limit infringement was recorded for a driver | Compliance officer, safety manager, and the driver themself |
| Tachograph download overdue | A driver-card (28-day) or vehicle-unit (90-day) data download is overdue | Compliance officer, safety manager, and the driver (for a driver-card download) |
| Return to base overdue | A return to base (driver every 4 weeks, vehicle every 8 weeks under the Mobility Package) is overdue | Compliance officer, fleet manager, and the driver (for a driver return) |
| New insurance offer | An insurer sent a new premium offer under a consent-gated data-sharing sync | Finance controller, fleet manager |
| Vehicle fault code | A vehicle reported a high-priority diagnostic trouble code (DTC) | Maintenance manager, fleet manager |
| Driver reply | A driver replied on a message thread tied to their assignment | Dispatcher, fleet manager, organization administrator |
| Re-route proposed | A disruption was detected on an in-flight route and a dynamic re-route was proposed | Dispatcher, fleet manager, organization administrator |
| Notification digest | A batched summary of several notifications for a user whose channel is set to daily/weekly digest mode | The user themself — generated automatically, not routed through alert rules |
In the background
Expiring documents and credentials are checked daily, ahead of their deadline, as are overdue tachograph downloads and returns to base. The remaining event types are created in real time, the moment the situation they describe occurs — e.g. immediately after a route is assigned or a safety event is confirmed.