Notifications

The Notifications page has two parts: Notification Rules, where you configure which events trigger an alert and how it's delivered, and Notification History, where you review everything that's already been sent.

Notification Rules

A notification rule watches for one event type on a set of vehicles and delivers an alert — in-app, by email, on the map, or any combination — to chosen team members whenever it happens.

Creating a Rule

Click Create Rule and fill in:

Event Type (Required): The event to watch for (see Event Types below)
Alarm Types: Only shown for the Alarm event type — optionally narrow the rule to specific alarm subtypes (e.g. SOS only) instead of matching every alarm. Leave empty to receive all alarm types
Window Start / Window End: Only shown for the Night Driving event type — the local time-of-day window (default 02:00–04:00) during which any vehicle movement triggers the alert
Silence Threshold (hours): Only shown for the Device Not Reporting event type — how many hours of silence trigger the alert (default 24)
Violation Types: Only shown for the Duty Hours Violation event type — optionally narrow the rule to specific checks (e.g. only the weekly cap) instead of watching all six. Leave empty to receive all violation types
Send Via (Required): One or more delivery channels — In-app notification, Email, and Show on map. Show on map isn't offered for the Duty Hours Violation type, since it's scoped by driver rather than a single vehicle location
Email Recipients: Team members who receive the email. Required if the Email channel is selected
Vehicles: Restrict the rule to specific vehicles. Leave empty to apply to all vehicles. Not shown for the Duty Hours Violation type, which is scoped by driver instead (see Drivers below)
Drivers: Only shown for the Duty Hours Violation event type — restrict the rule to specific drivers instead of vehicles. Leave empty to apply to all drivers
Enabled: Whether the rule is active

Click Create Rule to save.

Event Types

Fuel:

Fuel Drain — a fuel level drop that doesn't look like normal consumption, detected from your fleet's fuel sensor data
Fuel Filling — a fuel level increase, detected the same way

Driver Safety:

Seatbelt Not Used — seatbelt disengaged for more than 5 seconds while moving above 5 km/h. Requires a Seatbelt sensor configured for the vehicle (Fleet → Hardware → Sensors) — vehicles without one can't trigger this alert
Headlights Not Used — headlights off under the same duration/speed thresholds. Requires a Headlights sensor configured the same way
Night Driving — any movement inside the rule's configured time window (default 02:00–04:00)
Duty Hours Violation — flags when a driver crosses one of six duty/driving-hour limits: more than 4.5 hours of driving without a 30-minute break, more than 12 hours on duty or 10 hours driving within a rolling 24 hours, more than 80 hours on duty within a rolling 7 days or 120 hours within a rolling 14 days, or less than 24 continuous hours of rest within a rolling 7 days. Unlike every other rule type, this one is scoped by Drivers, not vehicles — driving/duty time is attributed to whichever driver's RFID/iButton badge the device reports (matched against the driver's Identifier), falling back to the vehicle's currently-assigned driver when no badge was swiped
Driver ID Missing — flags a vehicle's day once it's driven without an actual driver badge ever being read, relying on the vehicle's assigned driver instead. Only meaningful for vehicles with a badge reader installed — the Vehicles picker shows a tooltip on vehicles with a Driver Unique ID sensor configured, to help you pick the right ones. Fires at most once per vehicle per day

Device Status:

Status Online / Status Offline / Status Unknown
Device Inactive
Device Not Reporting — the device hasn't sent any position for longer than the rule's configured threshold (default 24 hours). Unlike Status Offline/Inactive (which follow your GPS platform's own timeout), this is a fixed, configurable silence window

Movement:

Device Moving / Device Stopped
Speed Limit Exceeded

Geofencing:

Geofence Entered / Geofence Exited

Engine:

Ignition On / Ignition Off

Other:

Alarm — SOS, accident, tampering, power cut/restored, hard braking/acceleration/cornering, and more. Optionally scope a rule to specific subtypes instead of all of them
Maintenance Required
Driver Changed
Command Result
Queued Command Sent
Media

Fuel Drain, Fuel Filling, and the Driver Safety types come from this app's own detection — Fuel from the same analysis used in the Fuel Report, and the Driver Safety types from a periodic sweep of recent vehicle activity (seatbelt/headlights every 2 minutes, night driving every 5 minutes, duty hours violation and driver ID missing every 15 minutes). Device Not Reporting is checked every 30 minutes against your platform's own last-received position, no GPS API calls needed. Every other type is reported directly by your GPS devices and relayed in real time as it happens — no extra configuration is needed here, but the underlying capability (e.g. a configured speed limit for Speed Limit Exceeded, or a maintenance interval for Maintenance Required) must already be set up on the device or vehicle for that event to ever occur.

Managing Rules

The rules table shows each rule's type, delivery channels, assigned vehicles, email recipients, and status. Use the search box to filter by type.

Each row's actions menu (⋮) has:

Edit — change any field of the rule
Enable / Disable — toggle the rule without deleting it
Delete — permanently remove the rule

Clicking a row also opens it for editing.

Vehicles and Recipients

Vehicles: Leaving this empty means the rule applies to every vehicle on the team, including ones added later. Selecting specific vehicles restricts the rule to only those.
Drivers: Only used by the Duty Hours Violation type. Leaving this empty means the rule watches every driver on the team, including ones added later. Selecting specific drivers restricts the rule to only those.
Email Recipients: Only current team members can be selected. If a selected member later leaves the team, they're automatically dropped from delivery.

If multiple enabled rules match the same event (e.g. two rules for the same type covering different vehicles), you still receive exactly one in-app notification and at most one map popup per event — email recipients across all matching rules are combined and each gets one email.

Notification History

Click View Notifications from the rules page to see everything that's been sent to your team.

Viewing History

The table shows each notification's type, title, message, and date. Use the search box to find notifications by content, and the Type column header to filter by a specific event type.

Read Status

Each row shows a mail icon indicating read or unread. Select one or more rows with the checkboxes and click Mark as Read to clear them.

Notification Shortcuts

Clicking certain notifications jumps you straight to the relevant page instead of just selecting the row:

Fuel Drain / Fuel Filling — opens the Fuel Report with that vehicle and day pre-selected, so you land directly on the relevant chart
Seatbelt Not Used / Headlights Not Used / Night Driving / Driver ID Missing — opens the Driver Safety report
Device Not Reporting — opens the Devices page

Deleting Notifications

Use the actions menu (⋮) on a row to delete it.

Delivery

In-app: Appears immediately in Notification History and as a live update if you're using the app at the time.
Email: Sent to each selected recipient's account email, queued for delivery.
Show on map: Flashes a small popup at the vehicle's marker on the Tracking page map, for a few seconds, if that vehicle is currently visible there. This is independent of In-app — you can select it on its own for alerts you only want a quick glance at while watching the map, without them cluttering Notification History or the unread badge. It only fires while someone actually has the Tracking page open at the moment the event happens; there's nothing to catch up on afterward.

Device and vehicle-activity events (everything except Fuel Drain/Filling, the Driver Safety types, and Device Not Reporting) are delivered in real time as they're reported — there's no delay for a scheduled check to run. Fuel and Driver Safety events run on a short periodic sweep (a few minutes' delay at most); Device Not Reporting is checked every 30 minutes.

Permissions

View rules: Requires the Notification Alert Rules: View permission (or team owner)
Create / edit rules: Requires the Notification Alert Rules: Create/Edit permission
Delete rules: Requires the Notification Alert Rules: Delete permission (or team owner)
View history: Requires Notifications: View, or is granted implicitly if you hold a permission tied to a specific notification type (e.g. Notification Alert Rules: View unlocks the device and vehicle-activity types including Device Not Reporting, Fuel: View unlocks Fuel Drain/Filling, Driver Safety Report: View unlocks the Driver Safety types including Duty Hours Violation and Driver ID Missing)
Update history (mark as read): Requires Notifications: Update
Delete history: Requires Notifications: Delete

If these options are not visible, contact your administrator to request access.

Documentation