Install and pair
Pairing has three parts: install the app in Slack, get a code from Slack, and paste it in the Claude console.1
Install the Claude app in Slack
Open claude.com/claude-for-slack, click Add to Slack, and approve the permissions Slack shows. Skip if the app is already installed.
2
Run @Claude connect in Slack
Send
@Claude connect in any channel, with no other text, either as a new top-level message or in a thread where Claude isn’t already working. In a DM with Claude, send connect on its own; link works in place of connect in both cases. Claude replies with a pairing code valid for 15 minutes. In a thread where Claude is already working, it treats the message as a normal request instead.Only a Slack workspace admin (or Grid org admin) can run this command. If that’s not you, send them the install request and have them return the code.If your install is missing a permission, the reply names it (and may still issue a code with a warning); see the section below.3
In the console: complete the pairing step
At
claude.ai/admin-settings/claude-tag, setup opens as a full page until your first workspace is paired; click Start setup to reach Pair your Slack workspace. Paste the code, choose where Claude can reply (Entire workspace (recommended) or Specific channel), and click Pair workspace. To pair a workspace after your first, select + Connect next to Where Claude Tag works instead, as described in Manage workspaces.Send the install request to your Slack admin
Steps 1–2 above need a Slack workspace admin; step 3 needs an Owner in your Claude organization. If those are two people, send the Slack admin this and have them return the code:If @Claude doesn’t respond at all
On Enterprise Grid, an earlier install can lose its connection and stop responding in every workspace. Don’t uninstall the app. Have a Slack Org Owner or Org Admin, while signed in to one of the workspaces (not the org-level admin page), open claude.com/claude-for-slack, select Add to Slack, and choose Install to entire organization. This refreshes the connection in place. Then send @Claude connect again in a channel of that workspace.
If @Claude connect says the installation is out of date
Your Slack install predates a permission the app now requests. The workspace keeps its old grant until a Slack admin approves the update. Replies name the missing permissions until then. The reply links both remedies; either one clears the error.
- Approve the updated permissions. A Slack workspace admin opens Slack’s installed-apps page,
https://app.slack.com/apps-manage/<team-id>/integrations/installed, finds the Claude app, and approves its requested permissions. The approves its updated permissions link in the reply lands on that page directly. On Enterprise Grid with an org-wide install, a Slack org admin useshttps://app.slack.com/manage/<grid-id>/integrations/installedinstead. - Reinstall the app. A Slack workspace admin clicks the reinstalls the Claude app link in the reply and approves the consent screen Slack shows. Opening claude.com/claude-for-slack and clicking Add to Slack again does the same thing. This installs over the existing app with the current permissions; do not uninstall first.
@Claude connect again. Slack’s Manage apps page lists the scopes the app requests, not the scopes your workspace has granted. Seeing a permission listed there does not by itself mean it is approved. The grant happens when an admin approves the update or completes the consent screen.
If Claude says Claude in Slack is not available for your organization
The reply “Claude in Slack is not available for your organization” means your Slack workspace is paired to a Claude organization with a restricted compliance configuration, such as Zero Data Retention (ZDR). Claude Tag retains channel memory and session transcripts, so it can’t run under that configuration. Check which Claude organization the workspace is paired to. If your company has more than one, for example a trial org alongside the main one, the workspace may be paired to the wrong one. An Owner in that organization can revoke the pairing so you can pair the workspace to the right one here. If the pairing already points to the intended organization, no admin setting lifts the restriction; contact your account team. If the reply instead says Claude Tag has been turned off for your Claude organization, the cause is the Enable Claude Tag for your organization toggle, and an Owner can turn it back on. See Claude Tag is turned off for your organization.If the console says “already connected to a different organization”
A Slack workspace can pair with only one Claude organization at a time, and this one is already paired elsewhere. An Owner in the Claude organization that currently holds the pairing must disconnect it from their Connected workspaces list before your code can be redeemed here. If your company has more than one Claude organization, check the others; the existing pairing is often in a test or trial org.If the console says “claim code is invalid, expired, or already used”
Pairing codes are single-use and expire 15 minutes after they’re issued. Ask the Slack admin to send@Claude connect again and paste the fresh code; reinstalling the app is not required. On Enterprise Grid, a Grid org admin’s reply includes a Grid-wide code (starting with enterprise_) alongside the workspace code (starting with workspace_).
If DMs never respond on Enterprise Grid
On Enterprise Grid, direct messages with Claude follow each user’s home workspace, not the workspace you paired. When a user is homed in a grid workspace the pairing doesn’t cover, their DMs answer with a redirect to setup instructions even after their account connects, while channels in the paired workspace work normally. The fix is to pair the whole grid rather than one workspace. Claude’s reply to a Grid Org Owner or Org Admin’s@Claude connect includes two codes; redeem the one starting with enterprise_ (not the workspace_ one) in the pairing step to cover DMs for users in every workspace of the grid.
After pairing: where Claude is enabled
Once a workspace is paired, where Claude responds depends on what you chose when pairing (entire workspace or specific channels), the Turn on Claude Tag toggle, and your access restriction setting.- What Claude can reach in each channel depends on which Access bundles you bind; see Configure per-channel access.
- Nothing runs until usage is funded on Team plans; see Set a spend limit.
- DMs work separately from channels and run on each user’s own claude.ai account. On Enterprise Grid, DMs follow each user’s home workspace; see If DMs never respond on Enterprise Grid.
Related resources
- Give Claude access: create an Access bundle and add connections
- What the Claude Slack app can access: the page to send a Slack admin who’s approving the install