Skip to main content

Notifications

Notifications are the department's automatic alerts about readiness rather than incidents: fewer than two drivers available, Engine 1 out of service, a member's staffing changed, inventory low, checklist missed. Each notification picks an event, a threshold and who to tell (everyone, a group, a role, specific people), and delivers through push, SMS and email.

Department menu → Notifications. Personal notification preferences (which channels you receive) are on your profile.

Notifications

Notification List​

Displays all configured notification rules with resolved human-readable descriptions of:

  • Who is notified
  • What triggers the notification
  • Threshold values

Creating Notifications​

Notification Targeting​

New notification

Notifications can target:

TargetDescription
EveryoneAll department members
Department AdminsOnly administrators
Selected Group AdminsAdmins of specific groups
Specific combinationsCustom mix of roles, groups, and individual users

Notification Event Types​

Event TypeDescriptionConfiguration
RolesInGroupAvailabilityAlertAlert when available personnel with a specific role in a group drops below thresholdRole, Group, Lower/Upper limits
UnitTypesInGroupAvailabilityAlertAlert when available units of a type in a group drops below thresholdUnit Type, Group, Lower/Upper limits
RolesInDepartmentAvailabilityAlertAlert when available personnel with a role department-wide drops below thresholdRole, Lower/Upper limits
UnitTypesInDepartmentAvailabilityAlertAlert when available units of a type department-wide drops below thresholdUnit Type, Lower/Upper limits

Threshold Configuration​

FieldDescription
Lower LimitAlert when count drops below this value
Upper LimitAlert when count exceeds this value

Current State Data​

When creating a notification, the system captures the current state of relevant resources (staffing levels, unit states) for comparison when evaluating triggers.

Matching statuses by meaning​

Rules on a personnel status, staffing level or unit status change, and the current states an availability alert counts, can pick a specific status or a meaning. The meanings are listed after your statuses as Any "On Scene" status, Any "Off Duty" status and so on. A meaning matches every status with that meaning, built-in or your own, in every status set. One rule then covers unit types with different custom statuses, and keeps working when you rename a status or add one with the same meaning. A status with no meaning only matches a rule that names it.

RulePick
Tell the chief when any unit goes out of serviceUnit status changed to Any "Unavailable" status (and Any "Maintenance" status)
Count available engines whatever their set calls itCurrent states Any "Available" status and Any "In Quarters" status
Watch members going off dutyStaffing changed to Any "Off Duty" status

Deleting Notifications​

Removes a notification rule by ID.

Display Resolution​

The notification list performs extensive resolution to display human-readable information:

  • Role IDs → Role names
  • Group IDs → Group names
  • User IDs → User names
  • Event type codes → Descriptive text
  • Unit type IDs → Unit type names

Setup examples​

Department typeHow to set it up
Volunteer fireRole availability below N for Driver/Operator (2) and Interior FF (4) → officers; Unit status changed to Out of service → chief and mechanic.
EMSUnit availability below 1 per station → supervisor; Inventory alerts → logistics role.
SARPersonnel staffing changed summary → coordinator daily; Group availability below N for Technical team.
Emergency managementWeather alert notifications by zone; Document added to the EOP category → all section chiefs.
SecurityUnit status changed (patrol out of service) → operations centre; Checklist missed → site supervisor.

Technical reference​

NotificationsController; routes /User/Notifications/{Index,New,Delete}; model DepartmentNotification (event type, threshold, target group/role/users, channels); evaluated by the notification worker on status/staffing/unit/inventory/checklist events. Status values in a rule (BeforeData, CurrentData) are tokens (StatusMatch): a status value, b + a base type for a meaning (e.g. b20 Maintenance), or -1 for any; the editor loads them from the Custom Statuses JSON endpoints with includeMeanings=true.

Interactions with Other Modules​

ModuleInteraction
Personnel RolesRole-based availability alerts
GroupsGroup-level availability alerts
UnitsUnit type availability alerts
Custom StatusesCurrent state data references custom states
Department SettingsNotification delivery channels
Contact VerificationNotification delivery is gated by each user's contact verification status per channel