Overview
Notification Settings lets each user control how they receive notifications inside Logsign USO. For every notification type, you can choose whether it appears in the Notification Center, as a popup, by e-mail, or by SMS. These preferences are personal: each user configures their own settings, and they do not affect what other users see.
The list of notification types you can configure depends on your license and role:
- If the Incident module is licensed, incident and task related events are available, including Incident Assign, Incident Close, Add contributors, Remove contributors, Priority Update, Task Assign, Task Reassign, Task Update, Task Status Update, Task Remove, Decision Assign, Decision Reassign, Decision Update, Decision Answer, Decision Remove, and Action Rule Failed.
- Administrators and other non standard user accounts also see system health check notifications: Index Service Status, Syslog UDP Service Status, Syslog TCP Service Status, Syslog TCP TLS Service Status, Syslog Stats, Data Collections, Disk Check, Collection Check, Persist Files Check, License Expire Check, Swap Usage Check, System Update, Daily Signed File Check, Daily Archive File Check, Weekly Signed File Check, Weekly Archive File Check, and Email Notification Check. If Leaf mode is enabled, Leaf Center Status and Leaf Status are included as well.
Accessing Notification Settings
- Click the notification (bell) icon in the top right corner of the header.
- Stay on the Event tab of the notifications panel. Notification Settings is only available from this tab, not from the System tab.
- Click Notification Settings at the bottom right of the panel.
Using Notification Settings
- Disable Notifications: a master switch at the top of the window. Turning it on suppresses every notification type at once and hides the table below it.
- Disable All / Enable All: links that turn every channel off or on for every notification type in one click. Use Save to apply the change.
- Per row channels: each notification type has its own checkmarks for Notification Center, Popup, E-Mail, and Sms. Click a checkmark to toggle it. Popup requires Notification Center to be enabled for that row: turning Popup on automatically turns Notification Center on as well, and turning Notification Center off automatically turns Popup off. E-Mail and Sms are independent and are not linked to the other columns.
Click Save once you are done to apply your changes. After the first save, an Audit row is added to the table with Notification Center and Popup enabled. This row is used for failed login attempt notifications.
Notes
- Settings are stored per user account. If a specific colleague should stop receiving certain notifications, that colleague needs to open Notification Settings from their own account.
- Incident and task related rows only appear when the Incident module is licensed on the instance.
- You never receive a notification for your own actions. If you assign an incident to yourself, close an incident yourself, or update your own task, no notification is generated for that action.
- The E-Mail and Sms columns only deliver messages if a default e-mail or SMS response integration is configured on the instance, under Settings > Integrations > Responses, with "default" enabled for that integration type. Notification Center and Popup do not depend on this.
What Each Notification Type Means
The incident related rows in the Tasks table correspond to specific events in the Incident, Task, and Decision workflow. The table below explains when each one fires and who receives it. System health check rows are not covered in this table.
| Notification Type | Fires when | Sent to |
|---|---|---|
| Incident Assign | An incident is assigned to a user | The newly assigned incident owner |
| Incident Close | An incident is closed | Every contributor on the incident, except the person who closed it |
| Add contributors | A user is added as a contributor on an incident | The user who was just added |
| Remove contributors | A user is removed from an incident's contributor list | The user who was removed |
| Priority Update | An incident's priority is changed | The incident owner and every contributor |
| Task Assign | A task is created, or an existing task's owner is changed | The new task owner |
| Task Reassign | An existing task's owner is changed to someone else | The previous task owner |
| Task Update | A task's description is edited | The task owner |
| Task Status Update | A task's status changes (Completed, Can't Complete, or Incomplete) | The task's creator |
| Task Remove | A task is deleted | The task's owner |
| Decision Assign | A decision is created, or an existing decision's owner is changed | The new decision owner |
| Decision Reassign | An existing decision's owner is changed to someone else | The previous decision owner |
| Decision Update | A decision's description is edited | The decision owner |
| Decision Answer | A decision is answered by its owner | The decision's creator |
| Decision Remove | A decision is deleted | The decision's owner |
| Action Rule Failed | An automated action rule, a playbook action tied to an incident, fails to run | Every user who has this notification type enabled, not just one person |
A few points are worth calling out because they are not obvious from the interface:
- Task Assign fires twice on reassignment. When a task's owner is changed, the new owner gets a Task Assign notification and the previous owner gets a separate Task Reassign notification. The same pattern applies to Decision Assign and Decision Reassign.
- Task Status Update goes to the creator, not the owner. If Alice creates a task and assigns it to Bob, Bob is the one who marks it complete, and Alice, the creator, gets notified that the status changed, not Bob.
- Decision Answer goes to the creator, not the owner. The owner is the one who answers the decision. The notification tells the decision's creator that it has been answered.
- Action Rule Failed is a broadcast, not a targeted notification. It is not tied to a specific incident owner or contributor. It goes out to every user who has this row enabled in their own Notification Settings, which is why it is enabled by default (Notification Center only) even before a user has ever opened this screen.