Notifications
Some things are worth knowing about but don't need anyone to act. A tag passed through a checkpoint, a vehicle reached a site, a sensor crossed a threshold for a moment. Notifications capture these: they tell your team something happened, with nothing to chase down afterwards.
Alerts vs notifications
Every rule produces one of two kinds of output, decided by its severity:
| Notification | Alert | |
|---|---|---|
| Severity | notification (the default) |
low, medium, high, or critical |
| What it's for | "Let me know this happened" | "Someone needs to deal with this" |
| Lifecycle | None — fire and forget | Active until resolved |
| Needs action? | No | Yes — acknowledge and resolve |
| Where it appears | Notifications page | Alerts page |
A notification fires, is delivered, and is recorded. There is nothing to acknowledge or resolve, and it never appears as an open item demanding attention. If instead you need the condition tracked until someone handles it, give the rule an alert severity and it becomes an alert.
When to use a notification
Choose the notification severity when:
- The event is informational — you want a record and a heads-up, not a task.
- The condition is momentary and self-correcting, so "resolving" it has no meaning.
- You're routing the event to an external system (via webhook) that does its own handling.
Choose an alert severity when the condition represents a problem that stays open until someone acts — a vehicle that hasn't returned, equipment outside a restricted area, a zone over capacity.
Because notification is the default severity, new rules notify unless you deliberately escalate them to an alert.
The Notifications page
The Notifications page is a chronological log of notification events. For each event it shows the tag or zone involved, the rule that fired, what happened, and when.
Unlike the Alerts page, there are no statuses, no Ack or Resolve buttons, and no counts of open items — notifications are events that already happened, not work to be done. Past notifications stay in the log for review and auditing.
Delivery
Notifications are delivered through the same channels as alerts — email, webhook, and the in-app experience. Each notification fires a single delivery when the rule triggers; there are no follow-up resolved or status_changed events because there is no lifecycle.
Set up channels and choose which a rule uses on the Event delivery page.
Notifications and reports
Because every notification is recorded, you can review how often a rule fired over a time window and include that history in reports — useful for confirming that checkpoints were passed or scheduled events occurred, without keeping a list of open alerts.