# Slack (/integrations/slack)

# Slack [#slack]

Someone posts a staging link in the design channel and asks what everyone
thinks. With Slack connected, Stunt Double answers in the thread: it opens the
page in a real browser, reviews it and replies with ranked findings. The same
Slack agent takes direct messages, answers questions about your workspace and
starts checklists and automations for you.

This page is the reference for connecting Slack and what it can do. For how a
review is triggered, steered and read, follow
[Review designs from Slack](/tutorials/slack-design-review).

## What it does [#what-it-does]

- **Direct messages.** Anyone in your Slack team can DM Stunt Double. Send a
  link and ask for feedback and it runs a design review. Ask about the
  workspace and it can start checklists and automations.
- **Design reviews in channels.** @mention Stunt Double with a link in any
  channel it has been invited to. In a channel turned on under design review
  settings, it picks up any message that carries a link and asks for
  feedback, no mention needed, and replies in the thread.
- **Figma links.** With [Figma](/integrations/figma) connected, a Figma link
  is rendered and reviewed, and a link to a selected frame reviews that
  frame. Web links are reviewed either way.
- **Notifications.** Workflow alerts go to a default channel, and each project
  can post to its own.
- **Workflow triggers.** Automations can start from Slack with the **Slack**
  trigger, on **App Mention** (someone @mentions Stunt Double) or **Message**
  (a message in the chosen channel).

## Before you start [#before-you-start]

- **Role.** Any member can install the Slack agent. Adding it to a Stunt
  Double workspace, or removing it, takes an owner or admin.
- **Plan.** Slack does not need a particular plan.
- **Slack access.** You need permission to install apps in your Slack team.
  If your Slack admins approve apps first, ask them to approve Stunt Double.

## Set it up [#set-it-up]

1. In [app.stuntdouble.io](https://app.stuntdouble.io), open **Integrations**
   from the sidebar and click **Slack**.
2. On **Your account**, click **Install Slack agent** and approve Stunt Double
   in Slack. The step changes to **Installed by you for** your Slack team.
3. On the step named after your workspace, an owner or admin clicks **Add**
   followed by your Slack team name. The step reads **On, through** your Slack
   team. One install serves every workspace it is added to, so a second
   workspace only needs **Add**, not another install.
4. On **Projects**, click **Choose for a project** and pick a project. Its
   **Settings** open on the **Integrations** tab: choose the project's
   **channel** there.
5. Under **Settings** on the Slack panel, pick a **Default channel** for
   notifications. A project's own channel overrides it, and with neither set,
   nothing is posted to a channel.
6. To have Stunt Double pick up review requests in a channel without a
   mention, open **Design review**, then **Settings**, and under **Channels**
   click **Add a channel**. **Try it** posts a test request in a channel so
   you can see the whole flow before your team uses it.

Guidelines marked **Apply to design reviews** on the **Guidelines** tab of
**Design review** are applied to reviews requested from Slack too.

Only the person who installed the Slack agent can browse the Slack team's
channels, because one install can serve several workspaces and the list covers
the whole Slack team. So the installer picks the default channel and project
channels; everyone else in the workspace sees where notifications go.

Setting Slack up for someone else? The card at the bottom of the Slack panel
gives you a link to share. It takes them through installing the Slack agent
for this workspace and choosing where notifications go.

## The Slack agent [#the-slack-agent]

Anything sent to Stunt Double that is not a link plus a request for feedback
goes to the Slack agent, in a direct message or as an @mention in any channel
it has been invited to. It works in one workspace, with the same read and
dispatch surface as the [MCP server](/mcp):

- List the projects, actors, checklists and automations in the workspace.
- Start a checklist run and hand back the run it created.
- Start an automation run.
- Start a design review for a link the review rules did not pick up.

Replies stream in as they are written. A thread is one conversation: every
follow-up in it continues the same session, so "run that one again" resolves to
the checklist you were just discussing. The direct message also pins a few
starting prompts to the top of the Messages tab.

Runs started from Slack are attributed to the person who asked, once they link
their Slack identity under their account's notification preferences. Runs from
anyone who has not are attributed to whoever installed the Slack agent, so link
identities before a team leans on this: attribution is what makes a run's
history legible a month later.

## What Stunt Double can access [#what-stunt-double-can-access]

The Slack agent asks for these scopes:

| Scope                                | Used for                                            |
| ------------------------------------ | --------------------------------------------------- |
| `channels:read`, `groups:read`       | Listing channels to choose from                     |
| `channels:history`, `groups:history` | Reading messages in channels it watches for reviews |
| `app_mentions:read`                  | Answering when someone @mentions Stunt Double       |
| `chat:write`, `chat:write.customize` | Posting replies, reviews and notifications          |
| `incoming-webhook`                   | Posting notifications to the channel you choose     |
| `im:history`, `im:write`             | Reading and answering direct messages               |
| `assistant:write`                    | Replying as an assistant in Slack's agent view      |
| `commands`                           | Handling Stunt Double's slash commands              |
| `users:read`                         | Showing who asked                                   |
| `mcp:connect`                        | Letting Slack reach Stunt Double's MCP server       |

Installs from before direct messages were supported lack `im:history` and
`im:write`. Under **Settings**, **Direct messages** shows **Reinstall the
Slack agent to turn this on** for those. Install again to grant them.

## Remove versus disconnect [#remove-versus-disconnect]

Slack has two ways out, and they reach different distances.

- **Remove** takes Slack out of one Stunt Double workspace. An owner or admin
  clicks **Remove** on the workspace step and confirms **Remove Slack from**
  the workspace name. Notifications and the Slack agent stop for that
  workspace. The install stays, so other workspaces keep using it and this one
  can be added back without installing again.
- **Disconnect** removes the install from your account, which takes it out of
  every workspace that uses it. The person who installed it clicks
  **Disconnect** on **Your account**, and the **Disconnect Slack?** dialog
  names each workspace that loses it. Notifications and the agent stop in all
  of them until someone installs it again.

To stop Slack in one workspace and leave the rest running, use Remove.

## Troubleshooting [#troubleshooting]

**A red banner reads "Slack has stopped working for" your workspace.** Slack
stopped renewing the install's token. Click **Reinstall the Slack agent**.
Reinstalling keeps every workspace that uses it.

**The workspace step reads "Not added here yet. Ask a workspace admin to add
it."** The Slack agent is installed, but only owners and admins can add it to
a workspace. Ask one of them to open the Slack card and click **Add**.

**Your account reads "Slack is linked to your account, but the Slack agent
install is gone."** The app was removed from Slack's side. Click **Install
Slack agent** to install it again.

**Stunt Double does not reply in a channel.** DMs work as soon as Slack is
added. In a channel, check that Stunt Double has been invited, then either
@mention it or add the channel under **Design review**, then **Settings**,
then **Channels**. If a channel there shows **Needs attention** and the page
asks you to **Reinstall to watch channels**, the install cannot read messages
in that channel, so only @mentions reach it until you reinstall.

**Direct messages do not arrive.** Check **Direct messages** under
**Settings** on the Slack panel. If it asks you to reinstall, the install
predates DM support.

**A channel picker reads "Only the installer can browse channels".** Ask the
person who installed the Slack agent to choose the channel, or install it
yourself.

**A review never starts.** If DMs and @mentions get answers but a review does
not, the message probably did not qualify as a review request. See
[When nothing happens](/tutorials/slack-design-review#when-nothing-happens).
