Notifications are configured in two places: Settings → Integrations (the channels themselves) and Settings → Recipients (groups of people).

Chat and collaboration channels

Under Integrations → Collaboration:

  • Microsoft Teams — incoming Webhook URL + channel name
  • Slack — Bot Token and Channel ID (webhook URL optional)
  • Google Chat — space webhook URL
  • Cisco WebEx — bot access token + room ID
  • Custom Webhook — POST to anything that accepts JSON

Each integration instance is named, so "NetOps Slack" and "Exec Slack" can coexist and be routed independently.

ITSM

Under Integrations → ITSM:

  • ServiceNow — instance URL, credentials, and an Assignment Group; alerts open incidents assigned correctly from the start
  • REST API — endpoint URL with bearer or basic auth, for home-grown ticketing

Email

SMTP is configured on the Metrics page alongside Metric Reports (host, port, implicit-TLS checkbox for port 465, username/password, from-address). Once set, email is available as an alert channel and for scheduled report delivery.

Browser push

Web Push sends native browser notifications with no third-party service — keys are generated and held by your own platform. Enable the opt-in toggle under Integrations → Collaboration, then each user opts in from their browser (including the mobile web app at /m). Select web_push as a channel in any rule or policy.

Recipient groups

Under Settings → Recipients, create groups like "NOC" or "Facilities — Region West":

  • Members come from your imported directory (Google Workspace, via a Cloud integration) or free-form external email addresses
  • A group can carry default channels and its own Google Chat space webhook

Recipient groups are selectable anywhere channels are — alert rules, routing policies, and sensor monitors — so "tell Facilities" stays one selection instead of a list of addresses that goes stale.

Routing policies

On Alert Rules → Notifications, combine channels and groups into named policies ("Business hours — chat only", "24/7 — page + ticket"). Rules that reference a policy inherit changes automatically; prefer policies over per-rule channel lists once you have more than a handful of rules.