Channel routing

By default, every alert mngd sends lands in the org’s alert_channel — the one you picked during the Slack install. Channel routing lets you split that single firehose into per-event channels so the right team sees the right thing.

Where it lives

Settings → Notifications → Org defaults → Channel routing.

The card shows a four-row table — one row per event type — with a channel dropdown and a Wording control on each. This page covers the dropdown; see Customize wording for the text overrides.

Pick a channel per event

Each row’s dropdown lists every public channel the bot can see, plus Use default (#alerts) at the top. Leave a row on Use default to keep that event flowing into your alert_channel; pick a specific channel to override.

Common splits we see:

• App update available → #patches or #it-announcements (the team patching apps wants to know what’s about to roll out).
• macOS release → #engineering-announcements or #allhands (a release worth telling everyone about).
• Endpoint offline → #it-alerts or #oncall (action signal).
• Fleet digest → #it-ops or #security-daily (read at a glance each morning).

Click Save routing to apply. Saves are atomic — mngd replaces the entire override set in one transaction, so a partial failure can’t leave you with half the rows pointed somewhere unexpected.

Private channels

Only public channels appear in the dropdown by default. To route to a private channel:

1. From inside the channel in Slack, run /invite @mngd.
2. Refresh the routing page in mngd.
3. The channel now shows up in the dropdown.

If you previously routed to a channel and the bot got kicked, the saved value stays in the dropdown as (not visible to bot) so you can see it’s still configured — re-invite the bot or pick a different channel to fix delivery.

Falling back to the default

The fallback chain is straightforward:

1. Per-event override (the row’s dropdown).
2. Org default (alert_channel from the Slack install).
3. No delivery — if neither exists, the alert is skipped.

You can change the org default any time from Settings → Integrations → Slack. Routing rows that point at Use default automatically follow.

Webhooks (legacy)

If your org also has a legacy Incoming Webhook configured under Settings → Integrations, channel routing does not affect it — the webhook URL has the channel baked into it by Slack. Webhook delivery always lands wherever the URL points. We recommend retiring webhooks in favour of the bot install since the bot path is what all the new features (DMs, interactivity, channel routing, wording overrides) build on.