Alert rules
Every event type has default routing (see the table in the notification center) — an alert rule lets you override it for the whole organization: change the channels, the recipient roles, add a numeric threshold, or turn a given event type off entirely.
Who it's for
A fleet manager or organization administrator creates, edits and deletes rules. Everyone else sees the list of configured rules read-only — so they can understand why a given event type reaches (or doesn't reach) certain roles.
Key concepts
An organization has at most one rule per event type. Until a rule exists, the built-in default routing applies; creating a rule is a clean override of that default — nothing needs to be turned off beforehand. A rule can also be disabled without being deleted: that's an explicit opt-out from notifications of that event type for the whole organization — no one receives them until the rule is re-enabled.
What a rule sets
An alert rule defines: which channels (in-app, email, SMS, push) the event is delivered on, which roles in the organization receive it, whether it should additionally reach the driver the event concerns (e.g. for an hours-of-service risk), an optional numeric threshold interpreted per event type (e.g. only fire when fewer days remain until expiry than the threshold), and a repeat-throttling window in minutes — repeats of the same event for the same subject inside that window collapse into a single notification, so a flapping sensor, for instance, doesn't flood recipients with dozens of identical alerts.
Deleting a rule restores the built-in default routing for that event type (see the table in the notification center) — an alert rule always only overrides that default routing; it is never the sole way to turn on notifications for a given event type.