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, set a numeric threshold where the event type uses one, 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, 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. Every event type has those three.
The other two are shown only where the event type in question uses them. "Notify the driver linked to the event" appears for event types that name a particular driver (e.g. an hours-of-service risk). "Threshold" appears where the notification has a number to compare against — today that's expiring driver credentials and expiring documents; in both cases it is a number of days until expiry, so the alert only fires when that many days or fewer remain.
A setting the form doesn't show is a setting that event type doesn't use — there's nothing to look for and nothing to fill in.
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.