Action Notifications
StationOne sends email notifications at several points in an action’s lifecycle. This guide explains who receives those notifications by default, and how brigade administrators can customise recipients to keep the right people informed without flooding inboxes.
When Notifications Are Sent
Section titled “When Notifications Are Sent”On Assignment
Section titled “On Assignment”When an action is assigned to a member, that member receives an email with the action details and a direct link to the action page.
This applies to all action categories and custom action types.
On Resolution
Section titled “On Resolution”When an action is resolved or closed, all watchers are notified. Watchers include:
- The member who originally reported or created the action
- Any member who has clicked Watch on the action detail page
Overdue — Assigned Actions
Section titled “Overdue — Assigned Actions”Once per day, members with overdue or approaching-due actions assigned to them receive a digest email listing all affected actions. This applies regardless of category.
Overdue — Unassigned Actions
Section titled “Overdue — Unassigned Actions”Once per day, unassigned actions that are past their due date trigger notifications to the relevant people for each category. See Default Recipients by Category below.
On Creation — System-Generated Actions
Section titled “On Creation — System-Generated Actions”Actions created automatically from inspections do not send a creation notification — the inspection report itself serves that purpose.
Actions created automatically from stock management (low stock) and pre-plan annual reviews do send a creation notification to relevant members. See Default Recipients by Category below.
On Creation — Manually Created Actions
Section titled “On Creation — Manually Created Actions”Manual actions do not send a creation notification by default. However, if a category has a custom notification config set up, the configured recipients are notified when a new action is created in that category.
On Creation — Custom Action Types
Section titled “On Creation — Custom Action Types”When a new action is created using a custom action type, the recipients configured for that type are notified immediately.
Default Recipients by Category
Section titled “Default Recipients by Category”When no custom configuration has been set for a category, notifications are sent to the following people.
Unassigned Overdue Notifications
Section titled “Unassigned Overdue Notifications”| Category | Default Recipients |
|---|---|
| Vehicle | Brigade and organisation admins; members with Vehicle Management permission |
| Equipment | Brigade and organisation admins; members with Equipment Management permission |
| BA Set | Brigade and organisation admins; members with BA View permission |
| Stock | Brigade and organisation admins; members with Stock Management permission |
| PPE & Uniform | Brigade and organisation admins; members with Stock Management permission |
| Pre-Plan | Brigade and organisation admins; members with Pre-Plan permission |
| Building & Maintenance | Brigade and organisation admins |
| IT | Brigade and organisation admins |
| Suggestion | Brigade and organisation admins |
| Other | Brigade and organisation admins |
Feature permissions are set per member via Appointments & Permissions.
Creation Notifications (System-Generated)
Section titled “Creation Notifications (System-Generated)”| Source | Default Recipients |
|---|---|
| Stock low-stock action | Admins; members with Stock Management permission |
| Pre-plan review action | Admins; members with Pre-Plan permission |
| Inspection failure action | No creation notification |
Configuring Custom Notification Recipients
Section titled “Configuring Custom Notification Recipients”Brigade administrators can override the default recipients for any system category. This is useful when you want a specific officer or working group to own a category rather than all admins being notified.
When a custom config is set for a category, it replaces the default for both creation and unassigned overdue notifications.
Steps to Configure
Section titled “Steps to Configure”- Navigate to Actions
- Click the Action Settings button (top right of the actions page)
- Scroll down to System Category Notifications
- Find the category you want to configure and click Configure
- Choose who should receive notifications:
- Brigade Admin — all brigade and organisation administrators
- Appointment Types — anyone currently holding one of the selected appointment types
- Specific Members — individually selected members
- Click Save Settings
The category row will show a notification indicator once a config is active.
To reset a category back to its defaults, click Reset next to the category. This removes the custom config and restores the standard behaviour described above.
Tips for Configuring Categories
Section titled “Tips for Configuring Categories”Use Appointment Types for roles that rotate. If your Vehicle Officer role is managed as an appointment type, selecting it here means notifications always go to whoever currently holds that role — you don’t need to update the config when personnel change.
Avoid over-notifying. The goal is to send notifications to people who can act on them. A Vehicle action going to the Vehicle Officer and their backup is more useful than going to every admin.
Categories without a feature requirement (Building & Maintenance, IT, Suggestion, Other) default to admins only, so if you have a Facilities Officer or an IT contact, configuring those categories is a good way to route those actions directly.
Custom Action Types
Section titled “Custom Action Types”Custom action types have their own notification config, set when the type is created or edited. The same three recipient options apply: Brigade Admin, Appointment Types, and Specific Members.
Custom action type notifications fire on creation and when actions of that type become overdue unassigned.
To manage custom action types, go to Actions → Action Settings → Custom Action Types.
See Manage Actions for general information on creating and working with actions.
User Notification Preferences
Section titled “User Notification Preferences”All action notifications respect each member’s personal notification preferences. Members can disable action notifications entirely or limit them to specific subtypes (such as overdue only) from their profile.
If a member is not receiving expected notifications, ask them to check their preferences.
See Manage Email Notifications for details.
Summary
Section titled “Summary”| Trigger | Who is notified |
|---|---|
| Action assigned | Assigned member |
| Action resolved or closed | All watchers |
| Overdue — assigned | Assigned member (daily digest) |
| Overdue — unassigned, no config | Admins + feature-permitted members (per category) |
| Overdue — unassigned, custom config | Configured recipients only |
| Creation — manual, no config | Nobody |
| Creation — manual, custom config | Configured recipients |
| Creation — custom action type | Configured recipients |
| Creation — stock or pre-plan auto action | Admins + feature-permitted members |