Configure page and global notification settings

Combine global channel setup with per-page delivery controls for Desktop, Slack, Teams, and Discord.

Last checked 20 August 2026

TechDash combines two layers of controls. The Notifications page makes a delivery channel available across the app. The Notify controls on each monitored page decide whether incidents routed through that page may use the channel.

Both layers must permit delivery. Turning a page toggle On does not create or enable a missing global webhook.

Configure global channels

Open Notifications from the sidebar.

  • Desktop notifications is a global On or Off control. It is On by default.
  • Notify when a check recovers controls qualifying recovery messages across all channels. It is On by default.
  • Slack webhook, Microsoft Teams webhook, and Discord webhook each accept a platform webhook URL. A non-empty URL makes that webhook available for incident delivery.
  • Send test appears beside each channel. For webhooks, the button is enabled after the field contains text. For Desktop, it is enabled when Desktop notifications is On.

Webhook fields are saved as you type. Clearing a field removes that global destination. TechDash trims and encrypts non-empty webhook URLs before storing them in its local app vault.

Configure one monitored page

  1. Open Websites and select the website.
  2. Find Monitored Pages.
  3. Expand the page you want to change.
  4. Under Notify, set Desktop, Slack, Microsoft Teams, and Discord independently.

New monitored pages default to all four toggles On. These controls affect notification delivery only. They do not enable or disable monitoring, change check frequency, alter incident severity, or remove an incident from TechDash.

Examples:

  • To keep native banners but stop chat messages for one page, leave Desktop On and turn the three webhook toggles Off.
  • To route one page only to Slack, leave Slack On and turn Desktop, Microsoft Teams, and Discord Off.
  • To stop Slack across every page, clear Slack webhook globally instead of editing each page.

How sitewide findings use page controls

Some findings belong to the website rather than a single URL, including site-resource and lookup issues. There is no separate website-level notification toggle.

TechDash looks for a monitored page with the path / and uses that page's notification controls. If no root page exists, it uses the first monitored page returned for that website. Keep that fallback in mind when configuring a website without a monitored homepage.

Other policy that can block delivery

Global and page controls do not override incident rules:

  • Built-in Advisory incidents remain in TechDash and do not notify.
  • Built-in Warning and Critical incidents can notify on a new failure or escalation.
  • Custom Checks use their own Notify option, independently of their chosen severity.
  • An ignored check does not appear in Incidents or send notifications.
  • Recovery messages require Notify when a check recovers to be On.
  • TechDash must be running when the result is produced.

An unchanged open failure does not send a new alert on every scheduled check.

Test your configuration

Use Send test on Notifications to check the global channel. Tests do not apply a page toggle, severity rule, ignored-check rule, or recovery rule. This makes them useful for isolating global configuration.

If a global test works but an incident does not arrive, investigate the page toggle and incident policy. If a webhook test is rejected before sending, check that the URL uses HTTPS and an allowed platform host.

Current webhook tests confirm that TechDash can issue the POST without a network exception or timeout. They do not inspect the remote HTTP status. Confirm the test message appears in the target channel before relying on that webhook.

Related articles