Notification rules and channels
Decide which resolver group each alert goes to, check who gets it with the simulator, and connect Teams, Slack, Telegram, or a webhook.
Notification rules decide which Resolver groups each incident goes to when it opens. Channels deliver those notifications to shared tools, and each person's preferences decide where the notifications reach them.
How the rule is chosen
The most specific rule wins, in this order:
An asset with a condition.
An asset.
An inventory group (with or without a condition).
That group's parent groups, from closest to farthest.
A source type (with or without a condition).
Finally, the default group.
If two rules are equally specific, the one with the higher priority wins. Without rules, everything goes to the default group.
The rule sets the incident's group when it opens. Changing the rules doesn't reassign what's already open; for that, an administrator can use Recalculate assignment on the incident.
Where notifications go
To each person: by email, browser push, and personal Telegram, according to their preferences in My notifications. All notifications also stay in their Received notifications inbox.
To the group email, if the group has one.
To the company channels: Microsoft Teams, Slack, Telegram (group or channel), and signed webhooks for tools such as PagerDuty, Opsgenie, GLPI, Jira, or n8n.
Teams, Slack, and Telegram receive the title, the severity, the asset, the group, and a link to ARGUNIS; never the detail or the evidence.