NetLock RMMNetLock RMM Docs
IV — Administration

Notifications deep dive

Full reference for the five notification channels on the Notifications page: Email (SMTP), Microsoft Teams, Telegram, ntfy.sh, and Webhook.

Notifications deep dive

The Notifications page at /manage_notifications is where every outbound alert leaves NetLock RMM. Five channels share the page as tabs (E mail, Microsoft Teams, Telegram, Ntfy.sh, and Webhook), and they all draw from the same event stream on the backend. This chapter documents each channel in depth, including the fields that differ between them, the test action, and the permissions that gate add, edit, delete, and test per channel.

If you only want a quick setup for the two most common channels, follow the How-To guide at H.10 — Configure email and Microsoft Teams notifications first and return here for the channels it does not cover.

Notifications page with the five channel tabs visible and the E mail tab active

A.8.1 The shared model

The rules in this section apply to every tab on the page.

Recipients are per-channel

Each channel manages its own list of recipients. A channel does not subscribe to a global recipient list: an email address you add on the Email tab does nothing on the Telegram tab, and vice versa. Add the same inbox to every channel you want it to receive alerts on.

Severity filters on the recipient, not on the event

Every recipient record on every channel carries a Severity dropdown with five options: Any, Critical, High, Moderate, and Low. The match is exact, not a threshold, and does not escalate. A recipient set to High receives High events only, not Critical ones. Only Any crosses severities and delivers events of every severity. To send two specific severities to the same destination without sending all of them, add that recipient once per severity, or use Any. Filtering happens on send, so a setting change affects future events only. Events already dispatched are not re-evaluated.

Tenant scope via drag-drop

Every recipient record has two side-by-side lists, Tenants on the left and Selected tenants on the right, with a drag-drop control between them. Drag a tenant into Selected tenants to scope the recipient to that tenant. Leave Selected tenants empty to receive events from every tenant.

An operator only ever works with tenants they can see. If your role is restricted to one tenant, the Tenants list shows that one tenant and that is the only scope you can assign; administrators with wider access see every tenant and can drag any combination across.

The Uptime Monitoring toggle

Every channel has a toggle labelled Uptime Monitoring on every recipient record. The tooltip reads "If 'Disconnection Alert' is enabled in the device overview, the event is forwarded." If the per-device Disconnection Alert flag (see Chapter 3.3) is on, device-uptime events will reach this recipient when the toggle here is also on. With the toggle off, uptime events bypass this recipient even if disconnection alerts are enabled on the device.

Routing, editing, and duplicates

  • Which event types a recipient receives depends only on its severity filter and its tenant scope. The page has no per-event-type routing.
  • Each channel is edited on its own tab.
  • Channels are not deduplicated against each other. A person who receives an event by email and by Teams gets two notifications.

A.8.2 Email (SMTP)

The E mail tab is the first tab on the page. Two things live here: a single global SMTP configuration for the entire deployment, and a list of per-recipient email records.

The global SMTP configuration

Click SMTP settings on the Email tab toolbar to open the SMTP settings dialog. Exactly one SMTP configuration exists per deployment; editing it replaces the previous configuration for every email recipient.

SMTP settings dialog with Server, Port, SSL/TLS, Username, Password, From address, To address, and Test controls

Fields in the dialog:

  • Server: SMTP hostname.
  • Port: SMTP port.
  • SSL/TLS: checkbox. Tick if the server requires TLS.
  • Username: SMTP authentication username. Some providers accept an email address here; others accept a distinct mailbox name.
  • Password: SMTP password, with a visibility toggle next to the input.
  • From address: sender address. This field is shown only when Username is not itself a valid email address, because some providers require an explicit From when the login name is not a mailbox.
  • To address: test-recipient address. Shown alongside From address under the same condition, and used only by the Test action.
  • Test: runs a live send. The Console sends a message with subject NetLock - Test Alert and body Test successful. to the To address (or to the first email recipient if the conditional fields are not shown). A snackbar reports Test successful. on pass or Test failed: <error> on failure.

The dialog's Confirm action is gated behind a successful test: you can save the configuration only after Test has passed in this dialog.

Tip: For providers that require app-specific passwords (Microsoft 365 with security defaults, Google Workspace with 2-Step Verification, some business ISPs), generate the app password first, paste it into Password, and leave Username as the full email address. The From address and To address extra fields should stay hidden for these providers.

Email recipients

The recipient table on the Email tab is where individuals and mailing lists get added. Add, Edit, and Delete row actions manage entries; the dialogs behind them all share the same fields:

  • E mail: recipient address.
  • Description: free text. Useful for listing a role ("On-call NOC engineer") rather than a person, so the row survives personnel changes.
  • Severity: one of Any, Critical, High, Moderate, Low.
  • Uptime Monitoring: toggle (see A.8.1).
  • Tenants / Selected tenants: drag-drop scope.

Multiple recipients are supported. The UI sets no cap; the practical limit is how many addresses your SMTP provider is willing to accept before rate-limiting you.

Test an email recipient

The per-recipient Test action is on the row itself. It reuses the global SMTP configuration to send the same NetLock - Test Alert message but to the recipient's address rather than to the To address field. Use this after adding a new recipient to confirm delivery reaches them specifically.

A.8.3 Microsoft Teams

The Microsoft Teams tab hosts a list of webhook connectors. Unlike Email, the tab has no global configuration dialog. Each Teams channel you want to post to is its own connector row.

Microsoft retired the classic Office 365 connectors in May 2026. Teams channels do not offer a connector configuration any more, and webhook.office.com URLs do not work. A channel takes webhook posts through the Workflows app instead: a Power Automate flow that starts with a webhook trigger and posts what it receives into the channel. H.10 walks through creating one.

Add Microsoft Teams Notification dialog with Connector Name, Connector-Webhook-URL, Payload format, Description, Severity, Uptime Monitoring, and tenant scoping

Fields per connector:

  • Connector Name: identifying name. Shown in test payloads and on notifications so recipients can tell which connector fired. Pick a name that describes the audience (NOC channel, Finance alerts) rather than the technology.
  • Connector-Webhook-URL: the URL the webhook trigger issued. Once saved, the value is masked in the table view and can be revealed only in the Edit dialog. The URL carries the binding to the flow along with its own signature, so regenerating it in Teams breaks the connector until the new URL is pasted over the old one.
  • Payload format: the shape of the body that is POSTed to that URL. Three options, described below.
  • Description: free text.
  • Severity: Any, Critical, High, Moderate, Low.
  • Uptime Monitoring: toggle (see A.8.1).
  • Tenants / Selected tenants: drag-drop scope.

Payload format

A Workflows webhook and a classic connector do not read the same body, and two flows built on the same trigger can disagree about what they expect. Payload format decides which body NetLock RMM sends:

  • Plain text (legacy connector): {"text": "…"}, the body the classic connector read. Teams does not accept it, but many other services do: Mattermost, Rocket.Chat, Google Chat and receivers of your own take a webhook URL and read a single text field.
  • Adaptive Card (Workflows webhook): the message envelope a webhook trigger expects, an object of type message whose attachments array holds one Adaptive Card. This is what a webhook created from the Workflows template needs, and the normal choice for a Teams channel.
  • Adaptive Card without envelope: the card on its own, starting at "type": "AdaptiveCard". A flow that hands the request body straight to its Post card in a chat or channel action needs this one, because that action accepts a bare card only.

The enveloped body has this shape; the body array carries the lines of the alert, and Adaptive Card without envelope sends the content object alone:

{
  "type": "message",
  "attachments": [
    {
      "contentType": "application/vnd.microsoft.card.adaptive",
      "content": {
        "type": "AdaptiveCard",
        "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
        "version": "1.4",
        "body": []
      }
    }
  ]
}

Connectors created before Payload format existed use Plain text (legacy connector). Switch such a Teams connector to the Adaptive Card format its flow needs (see the table below). A new connector opens with Adaptive Card (Workflows webhook) preselected.

Which option a Teams connector needs follows from how the flow behind the URL is built:

The flow behind the URLPayload format
The Workflows template unchanged: it posts the card it finds in the request's attachments.Adaptive Card (Workflows webhook)
A flow that passes the request body itself into Post card in a chat or channel.Adaptive Card without envelope
No flow at all — the URL belongs to a service that reads a text field.Plain text (legacy connector)

Over the Public API the field is payloadFormat, with the values legacyText, adaptiveCard, and adaptiveCardBare.

Note: A Workflows webhook posts as Flow bot. The display name and icon a classic connector could carry have no counterpart in Workflows, so every connector pointed at the same channel arrives under the same sender. Where it matters, let the Connector Name inside the message carry the distinction, or give each connector its own channel.

Test a Teams connector

The row Test action sends a test message in the connector's Payload format and names the connector in it. A snackbar reports Successfully sent on pass or Failed sending: <error> on failure.

A pass means the webhook accepted the call, which is not the same as the message reaching the channel. The webhook answers before the flow runs, so a flow that is turned off, or one whose post action cannot read the body it was handed, still produces a successful test. Open the Teams channel and confirm the message is there; if it is not, the flow's run history in Teams names the step that failed.

A.8.4 Telegram

The Telegram tab configures one or more bot-to-chat pairings. Each row represents a single Telegram bot posting into a single chat or group.

Fields per bot:

  • Bot Name: display name for this bot configuration. Used in test messages and snackbar feedback; does not have to match the name you gave the bot in BotFather.
  • Bot-Token: the Telegram Bot API token issued by BotFather. Password-masked in the table view; the dialog exposes a visibility toggle.
  • Chat-ID: target chat or group ID. Private chats have a numeric positive ID; groups have a negative ID; channels have a -100… ID. Password-masked.
  • Description: free text.
  • Severity: Any, Critical, High, Moderate, Low.
  • Uptime Monitoring: toggle.
  • Tenants / Selected tenants: drag-drop scope.

Multiple bots are supported. A common setup is one bot per region or per severity tier, each wired to a different chat.

Test a Telegram bot

The row Test action sends the text NetLock RMM Alert: Test.\nBot Name: <bot_name> to the configured Chat-ID using the configured Bot-Token. A snackbar reports Successfully sent on pass or Failed sending: <error> on failure.

Tip: A failed Telegram test often means that the bot has not been invited to the target group. Telegram bots cannot post into a group they are not a member of, even with a valid token and chat ID. Invite the bot first, then test.

A.8.5 ntfy.sh

The Ntfy.sh tab targets topics on ntfy.sh (or a self-hosted ntfy instance). Each row is one topic.

Fields per topic:

  • Topic Name: identifier and display name. Used in test messages and snackbar feedback.
  • Topic URL: the full ntfy URL for the topic. The public default looks like https://ntfy.sh/<topic>, but any ntfy-compatible URL works, including self-hosted instances. Password-masked in the table view.
  • Access Token: optional. When the topic requires authentication, paste a Bearer token here. The Console sends it as Authorization: Bearer <token> on every outgoing request. Leave blank for public topics. Password-masked.
  • Description: free text.
  • Severity: Any, Critical, High, Moderate, Low.
  • Uptime Monitoring: toggle.
  • Tenants / Selected tenants: drag-drop scope.

Multiple topics are supported. The usual pattern is one topic per on-call team or one topic per severity tier.

Test a ntfy.sh topic

The row Test action POSTs the plain-text body NetLock RMM Alert: Test.\nTopic Name: <topic_name> to the Topic URL. A snackbar reports success or failure. Subscribers who have the ntfy app open with a subscription to the topic see the test notification arrive live.

Note: ntfy.sh delivers push messages and does not keep them as a record. A notification sent before a subscriber opens the app on a fresh device is normally not replayed. For audit, rely on Events in the Console (see Chapter 12) rather than on ntfy history.

A.8.6 Webhook (notification channel)

The Webhook tab is the most flexible channel. Each row configures one outgoing HTTP call, with a freely edited request body and header set.

Add Webhook dialog with Monaco editors for Request Body and Request Headers and placeholder help text

Fields per webhook:

  • Name: identifier. Shown in the recipients table and in snackbar feedback.
  • Description: free text.
  • Severity: Any, Critical, High, Moderate, Low.
  • Url: the target URL. Unlike the other password-style fields on this page, the URL is shown in the dialog in clear text so it can be reviewed and corrected without toggling visibility.
  • Method: HTTP verb. Dropdown with GET, POST, PUT, DELETE, PATCH.
  • Request Body: JSON template. Edited in a Monaco editor with syntax highlighting. Runtime substitution replaces placeholder tokens with event data just before the call is sent.
  • Request Headers: JSON object. Defaults to {"Content-Type": "application/json"}. Edited in a Monaco editor. Keys and values are sent as HTTP headers on every call.
  • Sign requests: off by default. When on, every request carries the header X-NetLock-Signature, computed over exactly the body it sends. Switching it on generates a secret and shows it once; Rotate secret in the Edit dialog replaces it at once. The header name is reserved and cannot be set under Request Headers. Slack, Microsoft Teams, Discord and ntfy ignore signatures. X.10 shows how a receiver verifies them.
  • Uptime Monitoring: toggle.
  • Tenants / Selected tenants: drag-drop scope.

Placeholder tokens

Seven tokens are substituted into Request Body at send time:

TokenReplaced with
$netlock_tenant_nameName of the tenant the event belongs to.
$netlock_location_nameName of the location the event belongs to.
$netlock_device_nameName of the device that produced the event.
$netlock_dateTimestamp of the event, formatted per the deployment's date/time format (see A.5).
$netlock_reported_byIdentifier of the subsystem or user that raised the event.
$netlock_eventShort event type label.
$netlock_descriptionHuman-readable description of what happened.

Tokens are substituted literally. If your downstream system expects one of them to be wrapped in quotes for JSON validity, write the quotes into the template: "tenant": "$netlock_tenant_name" rather than "tenant": $netlock_tenant_name.

Test a webhook

The Add / Edit dialog has a Test Webhook button; the row in the table also has a Test action. Both actions parse the stored JSON and validate the URL. If both are well-formed, they send the call with the configured method, headers, and body. Validation failures surface as Invalid webhook URL. or Invalid JSON in Request Body.. A successful HTTP call produces a snackbar Webhook test successful! Status: <code>; a failed call produces Webhook test failed. Status: <code>. The test passes when the receiver answers with a 2xx status. Any other status, a 4xx answer for example, fails it.

A.8.7 Maintenance mode suppresses every channel

When maintenance mode is active (see A.2), none of the five channels fire. Maintenance mode applies to the whole installation, not to single tenants. The events are still written to the event stream and marked as read, so nothing is lost from the Console's history and they do not fire as a backlog when maintenance mode ends. What is suppressed is the outbound delivery. This applies equally to Email, Teams, Telegram, ntfy.sh, and Webhook. No channel can bypass maintenance mode.

A scheduled patch window with maintenance mode turned on keeps alerts for expected reboots away from operators and on-call channels. A genuine incident during the window is suppressed as well, so keep maintenance windows short.

A.8.8 The webhook channel is not the ticket webhook

NetLock RMM has two separate webhook systems.

Notification webhooksTicket webhooks
Configured onSettings → Notifications, Webhook tab (this chapter)Tickets → Departments, per-department webhook editor (Chapter 10.16)
Fires onGlobal events (device uptime, website uptime, port scanner, antivirus, job, sensor)Ticket events (ticket_created, sla_breached, etc.)
Tenant scopingDrag-drop on the recipient recordPer department
Placeholder format$netlock_*{{ticket_number}}-style
SignatureOptional, Sign requestsOptional, Sign requests

Pick the one that matches the event source. "Send every ticket update to Slack" calls for a ticket webhook. "Alert us when a device has been offline for ten minutes" calls for a notification webhook on this page.

A.8.9 Permissions

Every channel carries its own block of flags. A user without settings_enabled sees nothing in Settings; a user without settings_notifications_enabled sees no Notifications page at all; beyond that, each channel has independent add / test / edit / delete flags.

FlagGates
settings_enabledAccess to the Settings group.
settings_notifications_enabledAccess to /manage_notifications and its tabs.
settings_notifications_mail_enabledVisibility of the E mail tab.
settings_notifications_mail_smtpAccess to the SMTP settings dialog (Email-only sub-flag).
settings_notifications_mail_addAdd a mail recipient.
settings_notifications_mail_testTest a mail recipient.
settings_notifications_mail_editEdit a mail recipient.
settings_notifications_mail_deleteDelete a mail recipient.
settings_notifications_microsoft_teams_enabledVisibility of the Microsoft Teams tab.
settings_notifications_microsoft_teams_addAdd a Teams connector.
settings_notifications_microsoft_teams_testTest a Teams connector.
settings_notifications_microsoft_teams_editEdit a Teams connector.
settings_notifications_microsoft_teams_deleteDelete a Teams connector.
settings_notifications_telegram_enabledVisibility of the Telegram tab.
settings_notifications_telegram_addAdd a Telegram bot.
settings_notifications_telegram_testTest a Telegram bot.
settings_notifications_telegram_editEdit a Telegram bot.
settings_notifications_telegram_deleteDelete a Telegram bot.
settings_notifications_ntfysh_enabledVisibility of the Ntfy.sh tab.
settings_notifications_ntfysh_addAdd a ntfy.sh topic.
settings_notifications_ntfysh_testTest a ntfy.sh topic.
settings_notifications_ntfysh_editEdit a ntfy.sh topic.
settings_notifications_ntfysh_deleteDelete a ntfy.sh topic.
settings_notifications_webhook_enabledVisibility of the Webhook tab.
settings_notifications_webhook_addAdd a webhook.
settings_notifications_webhook_testTest a webhook.
settings_notifications_webhook_editEdit a webhook.
settings_notifications_webhook_deleteDelete a webhook.

The _smtp sub-flag on Email has no counterpart on the other channels. It exists because Email is the only channel with a single shared global configuration separate from the per-recipient records.

Payload format has no flag of its own either. It is a field on the connector record and follows the channel's add and edit flags like every other field in the dialog.