# How to Connect Slack to Claude: Setup and Permissions

*How-to — 2026-11-06 — by Mahmoud Zalt*

Add Claude to a Slack workspace, get the admin approval it needs, and understand exactly which channels and threads it can read.

**Short answer.** **You connect Slack to Claude by adding the Claude app from the Slack Marketplace, clicking Allow, then clicking Connect Account and signing in to Claude.** After that you mention @Claude in a thread or open a private conversation with it. On an Enterprise organization the install is different and an org admin has to allow it first.

Two things make this messier than it should be. The Claude experience inside Slack changed in 2026, so half the guides you find describe a version that no longer matches the buttons. And there are three separate ways to link Slack and Claude, each with its own approval, so people follow one guide and end up with a different result than the screenshot promised.

This guide sorts out which is which, then gives you the install path for a normal workspace and the separate path for an Enterprise organization. It also covers the part that matters most once it is running: how much of the conversation Claude can actually see, and which channels are off limits until someone deliberately opens them.

One framing note before the steps. What you are installing is an assistant you summon. It is very good at that. If you find yourself wanting the thing in Slack to own a recurring job rather than answer when tagged, you are describing an AI Employee instead, which is what we build at [Sistava](/features). Different tool, different expectations, and it is cheaper to know that on day one.

## Which connection do you actually want?

There are three. Claude inside Slack, where you tag it in channels and threads. The Slack connector inside Claude, where Claude on web or desktop reaches into your workspace. And the Slack MCP server, aimed at Claude Code and developer setups. Same two products, three doors, and each one is approved separately.

|  | Claude in Slack | Slack connector in Claude | Slack MCP server |
|---|---|---|---|
| Where you work | Inside Slack channels and threads | Inside Claude on web, desktop or mobile | Claude Code and Claude Desktop |
| Installed from | Slack Marketplace | Claude connectors | A plugin or connector setup |
| Who approves | Whoever may install Slack apps, or an org admin on Enterprise | The person connecting, plus workspace policy | Your Slack workspace admin approves the MCP integration |
| Typical use | Tag it in a thread, ask it to draft or summarize | Pull Slack context into a Claude conversation | Scripted and developer workflows |

**Checked August 2026.** Menu names, approval paths and context limits below were verified against Slack's own help pages and Anthropic's support docs in August 2026. Slack's help center states that Claude Tag replaces the previous Claude app in Slack from 3 August 2026, so older walkthroughs will not match. If a screen differs, trust the vendor pages listed under Sources.

## How do I add Claude to a normal Slack workspace?

Visit the Claude page in the Slack Marketplace, click Add to Slack, then click Allow to grant access. Return to your workspace when prompted, click Connect Account, and sign in to your Claude account. Slack's own documentation says any member with permission to install apps can add it, and anyone without that permission can send a request instead.

### Adding Claude to a standard workspace

1. **Open the Claude listing in the Slack Marketplace** — Go through Slack's Marketplace rather than a link someone pasted in a channel. Checking the publisher takes five seconds and rules out lookalike apps.
2. **Click Add to Slack** — Slack shows you which access the app is requesting. This screen is the only place you see the full list before agreeing to it.
3. **Click Allow** — This grants the app access to your workspace. If your workspace requires app approval, this turns into a request that an owner has to accept.
4. **Click Connect Account** — Follow the prompts to sign in to Claude, then come back to Slack. The Slack install and the Claude account are two separate things, and both are needed.
5. **Tag it in one thread** — Mention it in a real thread rather than a test channel. You learn more from one genuine question than from ten hello world messages.
6. **Decide where it lives** — Pick the two or three channels where it earns its place. Adding it everywhere at once is the fastest way to make people resent it.

If you are on an Enterprise organization, that flow does not apply. You click your organization name in the sidebar, select Tools and settings, then Manage apps. In the admin dashboard you click Manage apps again in the top right, search for Claude, click Continue, pick your workspaces from the dropdown, click Allow, then Add to Workspaces and select the target workspaces. You review the app scopes, approve them, and can optionally restrict access to specific members or groups.

## How much of the conversation can Claude see?

Less than most people assume, and that is deliberate. Slack's help page for Claude in Slack states that when you mention Claude in a channel it can access the 20 most recent messages, and in threads it can use the 50 most recent replies. Direct conversations with it are different, since there it has the conversation you are having.

Those numbers explain a common complaint. Someone tags it halfway down a 400 message channel, asks what was decided last month, and gets a confident answer about the wrong thing. It was not hallucinating from nothing, it was answering from a small recent window. Ask inside the thread that holds the context, not in the channel above it.

- **Private channels are opt in.** A Slack app cannot read a private conversation it has not been added to. Slack's developer docs are blunt about it: a bot token only reaches conversations the bot is a member of.
- **Other people's direct messages are never in scope.** No permission grant makes them visible, and no prompt gets around it.
- **Guests are excluded.** Slack states that guests cannot use AI apps or agents at all, so a contractor on a multi channel guest account will not see it.

## What changed with Claude Tag?

Claude Tag is the newer shape of Claude in Slack, and Anthropic describes it as available on Team and Enterprise plans in beta. The important difference is ownership. The older app ran under your personal Claude login. Claude Tag runs under an identity the organization provisions, with channel level controls an admin sets.

Anthropic's support documentation says that after the Claude app is installed, a Primary Owner or Owner sets up Claude Tag: provision Claude's identity, connect your organization's tools and repositories, and choose which channels Claude Tag can work in. So the person who installed the app is not necessarily the person who can finish the setup.

The admin controls are unusually specific and worth knowing before you pitch this internally. Admins can set per channel spend limits, configure which tools it can use per channel, view what it has remembered in a channel, and delete that memory. Anthropic notes that a private channel may need extra credentials or repositories on top of what the workspace already grants.

Billing splits along the same line. Anthropic's docs state that tagging @Claude in a channel is billed to your organization, while direct messages are billed to the person's own Claude account. That is a real budgeting detail: channel usage is a company cost with configurable limits, DM usage is not.

If the org identity, per channel scope and remembered context sound like a description of hiring rather than installing, that is because the whole industry is moving that way. It is the model [Sistava](/hire-ai-employees) has used from the start: you hire an AI Employee into a role, brief it once, and reach it wherever your team already works. Here is what picking a role actually looks like.

## What this will not do

It will not read your whole workspace history to answer a question. It works from a recent window plus whatever tools an admin connected, so a question that depends on something said six weeks ago in another channel will get a poor answer unless you paste the context in.

- **It will not install itself past your admin.** On Enterprise organizations, org level approval comes first, and no user side trick skips it.
- **Permissions do not carry over automatically.** Moving from the older Claude app to Claude Tag means tool connections and channel choices get configured again, not inherited.
- **It will not know your business unprompted.** Unless an admin connects your tools and repositories, it knows the thread in front of it and the general world, not your pricing or your policies.
- **Cost is not fixed.** Channel usage is consumption based, which is why the per channel spend limits exist. Set them before you invite it to a busy channel, not after.

None of this is a reason not to use it. It is a reason to roll it out channel by channel with a limit set, rather than switching it on everywhere and finding out what happens.

## FAQ

### Do I need a paid Claude plan to use it in Slack?

Slack's help page states that Claude in Slack is available on all Slack plans with a paid Claude account, and lists Pro, Max, Team and Enterprise. The newer Claude Tag experience is described by Anthropic as available on Team and Enterprise plans in beta. Because these lists change, confirm on the vendor pages before promising access.

### Why does it miss things that were said earlier in the channel?

Because it works from a recent window. Slack documents that a channel mention gives it the 20 most recent messages, and a thread gives it the 50 most recent replies. Ask inside the thread that holds the context, or paste the relevant messages into your question.

### Can it see my private channels?

Only ones it has been added to. Slack apps can read conversations they are a member of, and private channels have to be opened deliberately, one at a time. Under Claude Tag, a private channel may also need extra credentials configured by an admin.

### Who pays when someone tags it in a channel?

Anthropic's documentation says channel usage is billed to the organization, while direct messages are billed to the individual's own Claude account. Organizations can set overall and per channel spend limits, which is the control you want in place before a busy channel starts using it every day.

### What is the Slack MCP server, and do I need it?

It is a developer facing route that connects Slack to Claude Code and Claude Desktop. Slack's developer docs list one prerequisite that stops most people: access to a Slack workspace with the MCP integration approved by your workspace admin. If you are not writing code, you do not need it.

### Can an admin see what it remembered?

Under Claude Tag, yes. Anthropic states that channel and workspace memory is retained rather than discarded after each task, and that admins can review or delete what Claude remembers. That is worth telling your team before you turn it on rather than after.

## A sensible rollout

Start in one working channel with a spend limit set, tell the team it is there and what it can see, and give it a week. Watch for the requests it cannot fulfil, because those are the ones that tell you whether you needed an assistant or something that owns a job.

If the answer turns out to be the second one, look at what it costs to run a role rather than a chat window. Our own [plans and credits](/pricing) are laid out per role so you can compare like for like, and an AI Employee reachable in Slack is the same Employee you brief once in your dashboard.

One habit is worth building early. Whenever the assistant gets an answer wrong, correct it in the same thread rather than sighing and doing the task yourself. Under the newer setup that correction is part of what gets remembered in the channel, so the second month is meaningfully better than the first. Teams that skip this step end up concluding the tool is mediocre when what they really did was never teach it anything.

And keep the channel list short on purpose. An assistant in three channels where it is genuinely useful beats one in thirty where people have learned to scroll past it.

## Sources

- [Slack Help Center, Use Claude in Slack](https://slack.com/help/articles/53532192117267-Use-Claude-in-Slack) for the install steps, the Enterprise path, the plan requirement and the context limits.
- [Claude Help Center, What is Claude Tag?](https://support.claude.com/en/articles/15594475-what-is-claude-tag) for the owner setup, channel controls, memory and billing split.
- [Slack developer docs, Connect to Claude](https://docs.slack.dev/ai/slack-mcp-server/connect-to-claude/) for the MCP server route and its admin approval prerequisite.
- [Claude connectors, Slack](https://claude.com/connectors/slack) for what the connector can search, send and create.
- [Slack Help Center, Work with AI agents and assistants in Slack](https://slack.com/help/articles/33076000248851-Understand-AI-apps-in-Slack) for admin controls and the note that guests cannot use AI apps.
- [Slack developer docs, conversations.history](https://docs.slack.dev/reference/methods/conversations.history) for why an app only reads conversations it belongs to.

**Tags:** connect-slack-to-claude, slack-integration, workspace-permissions, ai-assistant-setup, ai-workforce-platform