@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
After the first pairing, the Set up button is gone. Use the Connected workspaces list instead.Open the pairing dialog
At
claude.ai/admin-settings/claude-tag, open the ⋮ menu on the Slack row under Where Claude Tag works and select Manage, then under Connected workspaces select +.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 in Slack version control.| Label | Effect |
|---|---|
| New | Claude Tag. Access bundles, skills, and custom instructions apply |
| Legacy | The earlier per-user Claude in Slack. Bundles and skills do not apply. Being deprecated; see Migrate from the earlier app |
| Off | Claude doesn’t respond to channel mentions in this scope. Direct messages are unaffected |
| Inherit | Use the parent scope’s value. Not shown at Default Slack access |
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.
Related resources
- Migrate from the earlier app: the upgrade path and what changes for existing users
- Pair your Slack workspace: the first pairing, with the Slack-admin handoff