Skip to main content
This page covers managing Slack workspace pairings after initial setup: adding more workspaces, choosing which Claude Tag version each one runs, and disconnecting one. 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. After the first pairing, the Set up button is gone and the Slack row appears under Where Claude Tag works. The reverse doesn’t hold. 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 as a new top-level message with no other text; sent as a reply inside a thread, the command is treated as a normal request and no code is issued. Paste the code Claude sends you into the dialog.
If your organization used the earlier Claude in Slack app, the dialog header reads Switch to Claude Tag instead of Set up Claude Tag for your workspace. The steps are the same, and 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.

​
Pair an Enterprise Grid

When a Grid Org Owner or Org Admin sends @Claude connect, the reply includes two codes. The workspace_ code pairs only the workspace it was sent from. The enterprise_ code pairs every workspace in the grid at once; redeem it when Claude should work across the grid. The choice matters for direct messages. On Enterprise Grid, DMs follow each user’s home workspace rather than the workspace you paired, so pairing a single workspace leaves DMs unanswered for users homed in the grid’s other workspaces. The enterprise_ code covers them all.

​
Set the version for a scope

Every scope routes to one of four versions. In the Claude Tag’s access section of admin settings, select the scope and use the Claude Tag version control.
LabelEffect
NewClaude Tag. Access bundles, skills, and custom instructions apply
LegacyThe earlier per-user Claude in Slack. Bundles and skills do not apply. Being deprecated; see Migrate from the earlier app
OffNeither version responds to channel mentions in this scope. Direct messages are unaffected
InheritUse the parent scope’s value. Not shown at Default Slack access
Both versions answer through the same @Claude app, so Off turns off the Legacy version too. To opt out of Claude Tag while keeping the earlier behavior, set the scope to Legacy, not Off. Per-scope version changes (workspace and channel) are reversible; see Migrate from the earlier app.

​
Revoke a pairing

In the Connected workspaces list, select Disconnect on the workspace’s row. Disconnecting revokes the pairing so @Claude no longer runs in that workspace, but the workspace’s scope and any bundles bound to it remain in the Slack tab; remove the scope separately if you want it gone. Claude stops responding in that workspace immediately. Its scopes remain in the Claude Tag’s access section, so credentials and instructions are preserved, until you remove them.