Slack now has an official door for AI. By default,
Claude walks through it with a copy of every key you hold.
Three checks before you open it: who approves, what Claude can read, and whether it can send. Claude can't click in
Slack for you, so the "Do it with Claude" card coaches you. You don't need to read the whole page. Paste the card and follow Claude.
01 / 08
What you're connecting
Slack launched its MCP server in February 2026. MCP is a standard plug that lets an AI app search and act inside another tool. Slack lists Claude as a supported client and says only directory-published or internal apps may use it.
Claude's
Slack connector is made by Slack, and its claude.com listing carries an Anthropic verified label. Inside Claude, verified connectors show a green tick next to the name. Anthropic's directory page says verification isn't a security audit.
The connector searches and reads messages. Slack's docs say it can also send, schedule and draft messages. Claude's listing and Slack's page both add that it creates canvases, Slack's shared documents.
It signs in as you. You sign in to Slack and approve the app, Slack returns only content you have access to, and
Claude inherits each person's permissions. As of October 2026.
- 3
- checks before Claude reads
- 1
- channel for your first test
- 20 min
- start to finish
Slack
At a glance
- Signs in as
- You
- Approval
- Your Workspace Owner or app manager may need to approve
- Time
- About 20 minutes with the checks
02 / 08
Check one: who approves it
Two people may need to say yes: someone in Slack and, on a
Claude Team or Enterprise plan, someone in Claude. Find your row.
| Your situation | Who says yes | What you see |
|---|---|---|
| You, if | Connect to | |
| You | Connect for your team, or Connect just for me from the arrow | |
| A | Team: Request, then Requested. Enterprise: Request, or a note to ask an Owner | |
| A Workspace Owner or app manager | A screen to request the app. | |
| Probably you, but |
On Slack's side, the default is open. Members can install apps without approval unless a Workspace Owner turns on "Only allow pre-approved apps". Slack's own Claude setup page still lists your workspace admin's approval as a prerequisite. The two pages disagree, so if you aren't the Workspace Owner, ask them before you connect.
When approval is on, requests go to Workspace Owners, and to any app managers they appoint.
Workspace Owners can switch approval on. It changes how everyone installs apps, so tell your team first.
In
Slack, open Admin › Apps and workflows › App management settings.
Next to Require approved apps, click Edit.
Tick Only allow pre-approved apps, then click Save.
Slack Enterprise+ with Okta and a
Claude Team or Enterprise plan uses a different flow, enterprise-managed authorization. Follow Slack's article for that one.
On Claude Team or Enterprise, an Owner adds a connector for the organization and members then connect their own account, per Anthropic's getting-started page. On Team, Request goes to your organization's Owners and becomes Requested. On Enterprise you may see a note to ask an Owner instead.
Anthropic says web connectors are available to all users, but its older Slack page says the Slack connector is for Team and Enterprise plans. If you are on Free, Pro or Max and Slack won't connect, that may be why. If you can't find Slack in Discover on Team or Enterprise, ask your
Claude Owner. As of October 2026.
If you need someone else's yes, send this.
03 / 08
Connect Slack
Do this part on a computer, with Claude's settings open in another window. Shorter steps for
Slack and
ClickUp together are in the workflow map guide.
If you want Claude to use a separate
Slack user instead of you, skip these steps. Use "Connect a tool as the AI user" in give your AI its own login instead, then come back for checks two and three. It uses a private window, so your own Slack sign-in can't slip in.
In the side panel of
Claude, click Customize.
Click Connectors.
Click Discover.
Search for
Slack and pick the result marked with a green tick.
Click Connect to
Claude.
Slack opens a screen asking you to sign in and approve access.
Sign in to
Slack.
Read the access
Claude asks for, line by line.
If you can untick private channels, DMs or group DMs, untick them. A first test doesn't need them.
Approve it.
Slack now shows as connected in Connectors.
Don't use Slack in a chat yet. Do checks two and three first.
04 / 08
Check two: what can it read?
Neither Slack's docs nor
Claude's docs describe a setting that limits this connector to channels you pick. Public search covers every public channel, even ones you never joined. So "only read #projects" typed into a prompt is a wish.
Slack does split search into four layers. Public channels are the required base. Private channels, DMs and group DMs are optional permissions with user consent. Slack hasn't published whether
Claude's approval screen lets you untick them one by one. Anthropic only says to review the access Claude asks for. That's why the connect steps say "if you can".
DiagramFour read layers
- Four read layers, with the Slack logo at the top: Public channels (base); Private channels (check what it asks for); DMs (check what it asks for); Group DMs (check what it asks for).
- The three lower layers sit behind a lock, with the label Not needed for a first test.
- Real limits: Blocked tools. Optional permissions you approve. Separate Slack user (limits private channels and DMs, not public ones).
Three limits are real, strongest first:
- Block the tools you don't need. Claude lets you choose Always allow, Needs approval, or Blocked for a whole group or for a single tool.
- Approve only the optional permissions you need. Owners and app managers choose which optional permissions to approve, and so do you wherever
Slack splits them.
- Give the AI its own
Slack user. It sees only the private channels and DMs that user is in. It still searches every public channel. The steps are in give your AI its own login.
The only documented per-channel control is a different product. Claude Tag responds only where it's been added and addressed. As of October 2026 it is a public beta for Team and Enterprise, set up by a Claude Owner. In channels it acts as its own identity, one Claude set up by an admin, not as you.
A wish vs a guardrail
A wish
- "Only read #projects" typed into the prompt
- "Stay out of my DMs" typed into the prompt
A guardrail
- The tool that searches private conversations set to Blocked (then run the limit test)
- Read tools on Needs approval, so you see every read
- Optional permissions you can decline, if
Slack's screen offers them
- A separate
Slack user for the AI (limits private channels and DMs, not public ones)
Now block the private search.
Open
Slack in your connector list (Customize › Connectors › Slack).
Find the three tool groups: Interactive tools, Read-only tools and Write/delete tools.
Set the whole Read-only tools group to Needs approval. It can show Always allow when you first open it, so check it.
Inside that group, set Search messages and files (the one that searches public and private conversations) to Blocked. Leave Search public messages and files as it is.
Claude's Slack listing names that search tool slack_search_public_and_private and its public-only sibling slack_search_public. On the connector page they show as Search messages and files and Search public messages and files. Blocking removes the search tool whose name says it covers private conversations. No one has published whether Claude can still open a private channel directly by its ID,
Slack's hidden address for it. That is why step 3 puts every read on Needs approval: Claude asks before each read, and you can say no. Check with the limit test.
05 / 08
Check three: can it send?
Slack's docs say the connector can send messages to any type of conversation and schedule messages for later. A scheduled message goes out while you aren't watching. So it needs approval like Send message.
In Slack, the Write/delete tools group holds Send message, Schedule message, Create a canvas and Update a canvas. The Interactive tools group holds Create a draft message.
| Group or tool | Examples | Set it to |
|---|---|---|
| Write/delete tools group | Needs approval | |
| Read-only tools | Tools that only read or search | Needs approval first. Always allow once you trust it. |
| Interactive tools | Needs approval first. Always allow once you trust it. |
The one exception is the tool that searches private conversations. It stays Blocked, per check two. Move the Read-only tools to Always allow only after a clean limit test (in "Your first week"). From then on, Claude reads without asking, so you can no longer say no to a single read. Keep the Write/delete tools group on Needs approval for good.
Open
Slack in your connector list (Customize › Connectors › Slack).
Find the three tool groups: Interactive tools, Read-only tools and Write/delete tools.
Set the whole Write/delete tools group to Needs approval.
Set Interactive tools, which holds Create a draft message, to Needs approval.
Check the mode. If your message box has a permission setting, set it to Manual. If it still shows separate Chat and Cowork options, pick Manually approve in Cowork. If you see neither,
Claude asks with an Allow once or Always allow prompt.
Slack's docs describe drafting as drafting, formatting and previewing messages directly within AI clients.
Claude may show the draft in the chat or save it in Slack's Drafts. Slack doesn't document which. Either way, nothing is sent until you approve.
DiagramClaude drafts, you approve
- Send messageNeeds approval
- Schedule messageNeeds approval
- Create a canvasNeeds approval
- Update a canvasNeeds approval
- Step 1, Claude shows the draft.
- Step 2, the approval prompt: Allow once or Always allow. Allow once is the choice. Always allow (not for sends) is crossed out.
- Step 3, the message appears in the channel in Slack.
- Slack's Write/delete tools group: Send message, Schedule message, Create a canvas and Update a canvas. All four are set to Needs approval.
On Team or Enterprise, an Owner uses the same page (Customize › Connectors › the tool) to limit actions for the whole organization, and individual users can't override it (Anthropic).
06 / 08
Your first week
Test with one channel you pick. Claude can still reach every public channel, so the limit is on you: ask only about that channel and check every answer. Widen after a clean week.
In
Claude, start a new chat.
Click + ("Add files, connectors, and more") at the lower left of the message box.
Click Connectors.
Toggle
Slack on. Connectors are switched on or off per chat. Check the toggle in every new chat, because Slack may already be on.
Paste this into
Claude, with your test channel filled in.
If Claude asks before a
Slack read, click Allow once. Check three things in each answer. The links open the real messages. Nothing comes from a place you didn't mean to share. Nothing was sent.
Now test your block.
In
Slack, create a private channel with only you in it.
Post one made-up word there, for example plum-test-42.
Back in
Claude, paste this.
It should find nothing. If it finds your word, switch Slack off in this chat, check that the private search tool shows Blocked, and test again. If it still finds it, disconnect Slack (see "How do I switch it off?").
After one clean week, add one more channel to your questions. Keep every send on Needs approval.
Confirm the setup works:
07 / 08
If it breaks
I see Request instead of Connect. What now?
Someone else has to approve it. On Claude Team, Request goes to your organization's Owners and becomes Requested. On Enterprise you may see a note to ask an Owner instead. If
Slack approval is on, the request goes to a Workspace Owner or app manager. Send them the message from check one.
My Slack admin can't find the request.
By default, only workspace owners can review app requests, unless they appoint app managers. A Workspace Admin who isn't an app manager may not see it. Send the message to an Owner.
Claude can't find an old message. Is it broken?
Maybe not. On Slack's Free plan you can view and search only the last 90 days.
Does using Slack through Claude count toward my Claude plan?
Yes. Everything you do with Claude counts toward your plan's usage limits, including searches and drafts in
Slack (Anthropic).
I use Claude Code. Do the same steps work?
Slack documents its own route with the Slack MCP and Skills Plugin, installed with
/plugin install slack. Connectors you add in claude.ai are also available in Claude Code when you sign in with the same Claude account.
Is this the same as @Claude inside Slack?
No. The earlier Claude in
Slack app and Claude Tag put Claude inside Slack. This guide puts Slack inside Claude. Anthropic's Slack page covers the earlier app.
How do I switch it off?
In Claude, open Customize › Connectors, open
Slack and click Disconnect. Then remove the app in Slack: your workspace name › Tools & settings › Manage apps › Installed apps › the app › App details › Configuration › Remove app. If approval is on, only Owners and app managers can remove apps. Removing the app takes it away for everyone in the workspace. To drop only your own sign-in, go to Configuration › Authorisations › Authorised members › See all › Revoke.
Claude quoted a DM or private channel I didn't mean to share.
Claude reads as you, so it can reach what you can reach. Switch
Slack off in that chat. Set the private search tool to Blocked, then disconnect and remove the app if you need to. Run the limit test again before you use it.
Finish line
What to do next
If you aren't the Workspace Owner, send the message from check one today. If you are, connect Slack, block the private search, set the Write/delete tools group to Needs approval, and run test question 1 in one channel before the day ends.
You reached the end of the guide