Skip to main content
This page covers managing Slack workspace pairings after initial setup: adding more workspaces, installing the app and pairing across a Slack Enterprise Grid, choosing which Claude Tag version each one runs, turning Claude on or off on the Team plan, and disconnecting a workspace. A workspace pairing links one Slack workspace (or Enterprise Grid) to your Claude organization so @Claude can run there. Your first pairing was created during setup. To add more, you must be an Owner in your Claude organization, and a Workspace Admin (or Grid Org Admin) in the Slack workspace you’re adding.

​
Pair another workspace

You can connect multiple Slack workspaces to one Claude organization. A Slack workspace or Enterprise Grid pairs with one Claude organization at a time. To move a pairing to a different Claude organization, an Owner in the organization that currently holds it must disconnect it first. Until then, the console refuses the new pairing as already connected to a different organization. Once the pairing moves, changes the previous organization’s admins make in their settings no longer reach that workspace. If your company has more than one Claude organization (a subsidiary with its own, for example), agree on which one holds the pairing before connecting.
1

Open the pairing dialog

At claude.ai/admin-settings/claude-tag, under Where Claude Tag works, either select + Connect at the top right, or open the ⋮ menu on the Slack row and select + Add workspace.
2

Get a pairing code from Slack

In any channel of the new workspace, send @Claude connect with no other text, as a new top-level message or in a thread where Claude isn’t already working, then paste the code Claude sends you into the dialog.Pick a channel that belongs to just the new workspace. Claude can decline to reply in guest and shared channels.
If your organization used the earlier Claude in Slack app, the new workspace is added alongside your existing one, not in place of it.
You’ll see: the new workspace in the Slack row’s connected list and as a scope in the Claude Tag’s access section.

​
Set up Claude Tag on Enterprise Grid

On Slack Enterprise Grid, installing the Claude app takes two Slack actions instead of one. A Slack Org Owner or Org Admin installs the app once for the entire Slack organization, then adds the installed app to each workspace where people will use Claude. After that, an Owner in your Claude organization pairs the whole Grid with a single Grid-wide pairing code.

​
Install the app across the Grid

1

Sign in to a workspace in the Grid

As a Slack Org Owner or Org Admin, sign in to one of the Grid’s workspaces rather than the Slack organization admin dashboard. Slack offers Install to entire organization only when you start from inside a workspace.
2

Install to the entire organization

On the Claude for Slack listing, select Add to Slack > Install to entire organization.If some workspaces in the Grid already installed the app on their own, leave those installations in place and choose Install to entire organization anyway. Don’t uninstall first, because uninstalling the app from a workspace deletes that workspace’s Claude data.
3

Add the app to each workspace

From the Slack organization admin dashboard, add the Claude app to each workspace where people will use Claude. Each workspace still needs the app added before people there can invite and mention @Claude.

​
Pair an Enterprise Grid

To get the Grid’s pairing codes, a Slack Org Owner or Org Admin sends @Claude connect, with no other text, in a channel of any workspace in the Grid. Claude’s reply includes two codes, one beginning enterprise_ and one beginning workspace_. The enterprise_ code pairs every workspace in the Grid that isn’t already paired on its own. The workspace_ code pairs only the workspace where @Claude connect was sent. Paste the enterprise_ code in one of these places:
  • During setup: paste the code into the Paste the pairing code field on the setup page
  • After setup: go to claude.ai/admin-settings/claude-tag > Where Claude Tag works > the Slack row’s ⋮ menu > + Add workspace, and paste the code into the dialog
Claude answers a one-to-one direct message according to the pairing of the sender’s home workspace, so only the Grid-wide pairing covers DMs from every workspace in the Grid. To move the Grid-wide pairing to a different Claude organization, an Owner in the Claude organization that holds it disconnects the Grid first. Disconnecting deletes the Claude-side data listed under Revoke a pairing for every workspace the Grid-wide pairing covered. Messages Claude already posted stay in Slack.

​
Turn Claude Tag on or off and set the version for a scope

Each scope has two controls, an Enable Claude Tag switch that turns Claude on or off there and a Claude Tag version setting that chooses which version answers while the scope is on. On the Team plan, a single Enable Claude Tag switch replaces them. Both controls are on the scope’s panel at claude.ai/admin-settings/claude-tag → Claude Tag’s access → Slack → the scope. Channels Claude was added to appear under Slack automatically, and the Search channels field finds a channel’s scope by name or ID. The Enable Claude Tag switch sits at the top of the scope’s panel. While the switch is off, Claude doesn’t respond to @-mentions in the scope. One-to-one direct messages from members who have connected a Claude account are unaffected. Turning the switch on routes the scope to New. To make a workspace or channel follow its parent again, click Use inherited setting under the switch. The Claude Tag version setting is under the scope’s Advanced section and is unavailable while the scope’s switch is off. Choosing Inherit clears the scope’s own setting entirely, so the scope also follows its parent for on or off. Both versions answer through the same @Claude app, so turning a scope’s Enable Claude Tag switch off silences the Legacy version there too. To opt out of Claude Tag while keeping the earlier behavior, leave the switch on and set the scope’s Claude Tag version to Legacy. Per-scope version changes (workspace and channel) are reversible; see Migrate from the earlier app.

​
Turn Claude Tag on or off on the Team plan

On the Team plan, you turn Claude on or off in every connected Slack workspace with one switch, at claude.ai/admin-settings/claude-tag → Claude Tag’s access → Slack → Default Slack → Enable Claude Tag. The switch doesn’t override a workspace whose own Enable Claude Tag switch is off. On the Enterprise plan, and in a Team organization whose Slack configuration can’t be expressed as one on-or-off choice (a scope set to Legacy, a workspace or channel set to New, a channel switched off, an access bundle attached to a channel, or a migration from the earlier Claude in Slack still in progress), the workspace and channel entries under Slack each show their own Enable Claude Tag switch and a Claude Tag version setting instead of the single switch; use Turn Claude Tag on or off and set the version for a scope.

​
Turn Claude off in channels

Go to claude.ai/admin-settings/claude-tag → Claude Tag’s access → Slack → Default Slack → Enable Claude Tag and turn the switch off. An @-mention in any channel gets “Claude is disabled in this channel” while the switch is off. One-to-one direct messages from members who have connected a Claude account keep working. To stop those too, turn off the Allow direct messages toggle. For members who haven’t connected an account, see Stop direct messages from members without a Claude account.

​
Turn Claude back on

Go to claude.ai/admin-settings/claude-tag → Claude Tag’s access → Slack → Default Slack → Enable Claude Tag and turn the switch on. Everything you set on each scope, such as access bundles and custom instructions, applies again. A workspace that was turned off on its own stays off, along with its channels.

​
Turn Claude off for the whole organization

Go to claude.ai/admin-settings/claude-tag and turn off the Enable Claude Tag for your organization toggle at the top of the page, above Claude Tag’s access. That toggle turns off direct messages too.

​
Keep Claude out of specific channels

The switch has no per-channel setting. Add blocked channel patterns for the channels instead.

​
Notices that settings aren’t applied

When a workspace or channel entry shows a notice that its settings aren’t applied, nothing you set there is lost.

​
Revoke a pairing

In the Connected workspaces list, select Disconnect on the workspace’s row, then confirm in the dialog. Claude stops responding in that workspace’s channels immediately, and your organization is no longer billed for Claude usage there. One-to-one direct messages from members who have connected a Claude account run on the member’s own account, so they keep working until the deletion below removes the member’s account link. A member who reconnects their account afterward can use direct messages again while the app stays installed.
When you disconnect a workspace, Anthropic deletes its Claude data:
  • The workspace’s sessions and their transcripts, including members’ direct-message conversations with Claude in that workspace
  • Its channel, workspace, and direct-message memory
  • The routines set up in its channels, and the artifacts published from them
  • Its scopes, with their instructions and bundle bindings
  • The links between members’ Slack and Claude accounts
Deletion starts as soon as you confirm and runs to completion in the background. This can’t be undone. Routines a person set up in a one-to-one direct message with Claude belong to that person’s account and keep running.
Access bundles belong to your organization, not to a workspace, so they stay available to attach to other scopes; only their bindings to the deleted scopes go. After you disconnect, the Slack row under Where Claude Tag works shows Disconnected with the workspace’s name, and offers a Reconnect action, as a button on that row and in the row’s ⋮ menu. Reconnect reopens the pairing dialog, where you redeem a fresh code from @Claude connect. The Slack app stays installed, so a workspace admin can pair the workspace again by sending @Claude connect in it, to the same Claude organization or a different one. If you intend the data to be deleted, wait a few minutes before pairing the workspace to the same organization again, because a new pairing that arrives while the deletion is still starting can cancel it. Once the deletion has run, the new pairing starts without the deleted data. Uninstalling the app from the workspace in Slack deletes the same data, whether or not you disconnected first; see Quiet or remove Claude Tag.