Connect Slack

mngd ships alerts through a Slack OAuth install — one click from Settings → Integrations → Slack. The bot token is stored encrypted and only ever lives in memory at delivery time.

Install the app

1. Sign in to the mngd portal as an admin.
2. Go to Settings → Integrations.
3. On the Slack card, click Connect.
4. You’ll be redirected to Slack’s OAuth flow. Approve the requested scopes for your workspace.
5. Back in mngd, the card now shows Connected with the workspace name.

Pick the default channel

After the install completes, the Slack card asks for an alert channel. This is where every alert goes by default — until you set per-event overrides on Channel routing.

• Pick the channel from the dropdown. mngd reads the list via Slack’s conversations.list, so any public channel in the workspace is selectable.
• For a private channel: invite the mngd Slack app to the channel first (/invite @mngd from inside Slack), then refresh the picker — private channels the bot can see show up the same way.

What’s required for delivery

For an alert to land in Slack, three things must be true:

1. The Slack app is installed for the org (you just did this).
2. A channel is set — either the default alert_channel or a per-event override.
3. The mngd bot is invited to that channel. If the bot was kicked or the channel is private and the bot was never invited, mngd’s delivery fails silently with not_in_channel.

If alerts stop landing, the first thing to check is whether the bot is still in the target channel. The portal won’t catch this — Slack just rejects the post.

Removing the integration

The same card has a Disconnect button. This:

• Revokes the OAuth token with Slack.
• Marks slack_bot_installations.enabled = false so postings stop immediately.
• Leaves your channel routing and wording overrides intact, so reconnecting later picks them up where you left off.