# Slack

Connect Slack for outbound event notifications.

Source: https://statusdashboard.com/docs/integrations/slack

> This is a plan-gated feature. If it isn't available in your account, visit the [Billing](/docs/org-mgmt/billing) page or contact support to review your options.

Slack integration posts event notifications to a channel in your workspace using Block Kit messages. StatusDashboard connects through OAuth: you authorize the app once per workspace, then pick a destination channel for each subscription. Register channels from [Slack channels](/app/integrations/slack/channels), or let visitors subscribe from a status dashboard when the channel is enabled.

For Block Kit format and delivery logs, see [Slack notifications](/docs/notifications/slack). For the public `/subscribe` flow, see [Slack subscriptions](/docs/status-dashboards/subscriptions/slack).

***

## One workspace, many channels
Slack delivery is registered **per channel**, not per workspace.

| Concept                  | What it means                                                                                                                                                                                                                                |
| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Workspace install**    | OAuth installs the StatusDashboard app on a Slack workspace once. The same install is reused when you connect additional channels in that workspace.                                                                                         |
| **Channel subscription** | Each destination channel is a separate subscriber row: its own management email, component selection, pause/suppress state, and delivery logs.                                                                                               |
| **One channel per flow** | Each **Connect Slack** or **Add to Slack** run authorizes the workspace (if needed), then the channel picker lets you choose **one** channel. To add another channel in the same workspace, run the flow again and pick a different channel. |

Most organizations start with a single channel (for example `#status` or `#incidents`). Multiple channels are supported when different teams or audiences need separate destinations. Each unique `(workspace, channel)` pair is a separate registration in your organization.

List views show **`#channel-name · Workspace Name`**. Bot tokens are never shown in the admin console.

## Connecting a channel (OAuth)
Connect StatusDashboard to a Slack workspace with **OAuth**, then pick exactly one destination channel for that subscription.

1. Click **Connect Slack** (admin) or **Add to Slack** (public subscribe on a status dashboard).
2. Authorize StatusDashboard in Slack (or confirm if the app is already installed on the workspace).
3. On the channel picker, choose the single channel where updates for **this** subscription should post, then complete the flow.
4. **Public channels:** StatusDashboard joins the channel automatically when the subscription is created. **Private channels:** invite the app in Slack before the channel appears in the picker; see [Slack subscriptions](/docs/status-dashboards/subscriptions/slack) for the visitor flow.

To register a second channel in the same workspace, repeat from step 1. You are creating a second subscription, not extending the first one.

## Managing subscribers
Organization admins and users with the **subscriber** role can register **pre-verified** Slack channels from [Slack channels](/app/integrations/slack/channels). OAuth completion marks the row verified immediately.

| Field                      | Meaning                                                                                                                                     |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| **Dashboard**              | Status dashboard the subscription belongs to                                                                                                |
| **Slack channel**          | Workspace + channel selected after OAuth (`displayName`)                                                                                    |
| **Management email**       | Contact for manage links; receives a **failure alert email** when a channel is auto-suppressed (see [Suppression](#suppression))            |
| **Components**             | At least one component on that dashboard; event notifications deliver when the event affects an overlapping component                       |
| **Pause deliveries**       | When paused, event notifications are skipped for this channel until an admin resumes delivery from the edit dialog (pencil icon on the row) |
| **Admin-managed (locked)** | When locked, public subscribe and manage flows on the status dashboard cannot change the subscription                                       |

Use the **pencil** icon on a row to change components, pause or resume deliveries, or toggle the locked flag. The **list** icon shows the current component selection read-only.

## Suppression
After **5 consecutive** failed event-notification deliveries, StatusDashboard automatically suppresses the channel:

* Future deliveries are skipped until suppression is cleared.
* The subscriber row shows a suppressed status.
* The **management email** receives **one alert email** (not one email per failed delivery).

StatusDashboard does **not** email the management address for individual failures before suppression. Use [Slack delivery logs](/app/notifications/slack/logs) to review per-attempt outcomes.

Review or clear suppressed channels on [Slack suppression](/app/integrations/slack/suppression).

### Failure alert email
When suppression triggers, the management email receives a message that Slack notifications were disabled for that channel. The email includes:

* The status dashboard name and the **channel display** (`#channel · workspace` — never bot tokens)
* The consecutive failure count that triggered suppression
* The last failure reason when available (for example, `channel_not_found`)
* A **Manage subscription** link when a signed manage URL is available; otherwise instructions to request a new manage link from the status page

Clear suppression entries on [Slack suppression](/app/integrations/slack/suppression), or unsuspend from the public manage page, after fixing the Slack channel (re-invite the bot, un-archive the channel, etc.). Clearing suppression does **not** resend missed notifications.

> Suppression blocks delivery to specific 
>   **channels**
>    until cleared. It is separate from 
>   **Pause deliveries**
>    (admin edit dialog only) and from turning 
>   **Notifications**
>    off on an event.