# Slack

Let visitors subscribe a Slack channel on your status dashboard.

Source: https://statusdashboard.com/docs/status-dashboards/subscriptions/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.

This page covers the public **Subscribe** and manage flows for Slack on your status dashboard. For OAuth setup, admin registration, and suppression, see [Slack integrations](/docs/integrations/slack). For Block Kit format and delivery logs, see [Slack notifications](/docs/notifications/slack).

***

## What visitors see
Slack subscriptions let visitors connect a Slack workspace, pick a destination channel, and receive Block Kit updates when matching events are created or updated.

Unlike webhook, Teams, or Google Chat, there is **no webhook URL field**. The flow is **OAuth-only**.

On `/subscribe`, visitors with the Slack channel effectively enabled see a **Slack** tab where they:

1. Enter a **management email** used for manage links and delivery-failure alerts.
2. Select one or more **components** from your dashboard (grouped when component groups are enabled).
3. Accept consent and terms checkboxes.
4. Complete the **reCAPTCHA** check when the dashboard is public (SSO off).
5. Click **Add to Slack** and complete authorization in Slack.
6. Pick exactly **one** destination channel when prompted, then finish the flow.

Each **Add to Slack** run registers one channel. To add another channel in the same workspace, run the flow again and choose a different channel.

**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.

They must select at least one component before starting OAuth. On public dashboards, **Add to Slack** stays disabled until reCAPTCHA is completed.

Below the subscribe form, an **Already subscribed?** section lets returning managers enter their management email and click **Manage** to receive a link for updating preferences.

## OAuth activation
Slack subscriptions are verified when OAuth completes — there is no separate verification step after authorization. Deliveries can begin as soon as the channel is connected.

If authorization is cancelled or the channel step fails, the visitor can start again from the **Slack** tab on `/subscribe`.

## Managing preferences
After OAuth — or after requesting a manage link — visitors land on the Slack manage page from the email link (token valid for **1 hour**). Managers can change components (deselecting all stops notifications without deleting the subscription), clear suppression after fixing the channel (**Resume deliveries**), or request a new manage link later.

They **cannot** repoint the Slack channel or rotate bot tokens from manage. If the app was removed from the workspace or channel, reconnect with **Add to Slack** from the subscribe page.

When a tenant admin has **paused deliveries** for this channel in the admin console, the manage page shows a read-only notice. Visitors cannot clear that pause from manage; they can still change component selections while paused.

Each new manage-link email **revokes** any previous management link for that subscriber.

### Pausing deliveries
Slack channel subscriptions support pausing deliveries in a few different ways.

| Who                        | How deliveries stop                                                                                                                                            |
| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Tenant admin**           | **Pause deliveries** in the admin console ([Managing subscribers](/docs/integrations/slack#managing-subscribers)). Component selections stay unchanged.        |
| **Visitor (manage page)**  | Deselect all components and save.                                                                                                                              |
| **Platform (suppression)** | After repeated delivery failures ([Suppression](/docs/integrations/slack#suppression)). Use **Resume deliveries** on the manage page after fixing the channel. |

Admin pause, an empty component selection, and suppression are independent. Clearing suppression does not resume an admin pause.

## Subscriber limits
* Each **new** unique `(workspace, channel)` pair consumes one slot when the subscription is created.
* The same channel cannot subscribe on a **second** status dashboard in the same organization while it is already registered elsewhere.
* When the limit is reached, new channels are rejected at subscribe time.

## What admins control vs. what visitors control
| Setting                                 | Controlled by                                                               |
| --------------------------------------- | --------------------------------------------------------------------------- |
| Whether Slack subscriptions are offered | Plan (**integrations**) + dashboard **Subscriptions** tab toggle            |
| Which components a channel watches      | Visitor (unless **admin-managed / locked**)                                 |
| Pause deliveries                        | Tenant admin only — see [Pausing deliveries](#pausing-deliveries) above     |
| Admin-managed (locked) subscriptions    | Admin — [Slack integrations](/docs/integrations/slack#managing-subscribers) |

**Admin-managed** channels are registered on [Slack channels](/app/integrations/slack/channels). Locked subscribers continue to receive notifications but cannot use the public subscribe or manage flows.

## Security notes
* When SSO is enabled, visitors must authenticate through your IdP before using subscribe or manage APIs. reCAPTCHA is not shown on SSO-protected dashboards.
* On **public** dashboards (SSO off), subscribe and manage-request forms require reCAPTCHA.
* Treat manage links like password-reset links. Do not share them.
* Bot tokens are never shown on the status dashboard or in manage flows.
* IP allowlist rules still apply to subscribe traffic when configured.