Manage workspaces and versions changedclaude-tag/admins/workspaces
Nearest release: v2.1.295, published an hour before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 8 Oct 2026 19:35 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 20 Oct 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+40added
Lines−40removed
From line
2
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits21to this page, all time
The whole hunk
from line 2, old and new numbered
/
from line 2
22
33> Connect more Slack workspaces or an Enterprise Grid to Claude Tag, choose which Claude Tag version each channel uses, and disconnect a workspace.
44
5export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
5> [!NOTE]
6>
7> Claude Tag is in public beta. Features and behavior described here may change before general availability.
68
7<BetaNote />
8
99This 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.
1010
1111A 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](/docs/claude-tag/admins/setup-overview). 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.
from line 20
2020
2121If your company has more than one Claude organization (a subsidiary with its own, for example), agree on which one holds the pairing before connecting.
2222
23<Steps>
24 <Step title="Open the pairing dialog">
25 Go to [**Claude's access > Channels > Slack**](https://claude.ai/admin-settings/claude-tag/channels/slack). On the **General** tab, under **Connected workspaces**, click **Connect new**.
26 </Step>
23**1. Open the pairing dialog**
2724
28 <Step title="Get a pairing code from Slack">
29 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.
25Go to [**Claude's access > Channels > Slack**](https://claude.ai/admin-settings/claude-tag/channels/slack). On the **General** tab, under **Connected workspaces**, click **Connect new**.
3026
31 Pick a channel that belongs to just the new workspace. Claude can decline to reply in [guest and shared channels](/docs/claude-tag/admins/troubleshooting#guest-and-shared-channels).
32 </Step>
27**2. Get a pairing code from Slack**
3328
34 <Step title="Finish the dialog and launch">
35 Once the code is accepted, click **Next**, work through the dialog's remaining steps, and click **Launch Claude** on the last one.
36 </Step>
37</Steps>
29In 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.
3830
39<Note>If your organization used the earlier Claude in Slack app, the new workspace is added alongside your existing one, not in place of it.</Note>
31Pick a channel that belongs to just the new workspace. Claude can decline to reply in [guest and shared channels](/docs/claude-tag/admins/troubleshooting#guest-and-shared-channels).
4032
33**3. Finish the dialog and launch**
34
35Once the code is accepted, click **Next**, work through the dialog's remaining steps, and click **Launch Claude** on the last one.
36
37> [!NOTE]
38>
39> If your organization used the earlier Claude in Slack app, the new workspace is added alongside your existing one, not in place of it.
40
4141**You'll see:** the new workspace in the **Connected workspaces** list with the status **Active**, and as a row on the **Channels** tab.
4242
4343## Set up Claude Tag on Enterprise Grid
from line 46
4646
4747### Install the app across the Grid
4848
49<Steps>
50 <Step title="Sign in to a workspace in the Grid">
51 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.
52 </Step>
49**1. Sign in to a workspace in the Grid**
5350
54 <Step title="Install to the entire organization">
55 On the [Claude for Slack](https://claude.com/claude-for-slack) listing, select **Add to Slack > Install to entire organization**.
51As 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.
5652
57 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](/docs/claude-tag/concepts/data-lifecycle#actions-in-slack).
58 </Step>
53**2. Install to the entire organization**
5954
60 <Step title="Add the app to each workspace">
61 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`.
62 </Step>
63</Steps>
55On the [Claude for Slack](https://claude.com/claude-for-slack) listing, select **Add to Slack > Install to entire organization**.
6456
57If 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](/docs/claude-tag/concepts/data-lifecycle#actions-in-slack).
58
59**3. Add the app to each workspace**
60
61From 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`.
62
6563### Pair an Enterprise Grid
6664
6765To 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.
from line 69
7169* **During setup:** paste the code into the **Paste the pairing code** field on the [setup page](/docs/claude-tag/admins/setup-overview#pair-your-slack-workspace)
7270* **After setup:** click **Connect new** under **Connected workspaces** on the **Slack** page, as in [Pair another workspace](#pair-another-workspace), and paste the code into the dialog. If a workspace you've already paired belongs to a Grid you haven't paired, the list also has an **Enterprise Grid** row with the status **Not connected**, and **Connect** on that row opens the same dialog.
7371
74<Note>Leave the workspaces you've already paired connected while you pair the Grid. They stay paired and keep their Claude data.</Note>
72> [!NOTE]
73>
74> Leave the workspaces you've already paired connected while you pair the Grid. They stay paired and keep their Claude data.
7575
7676**You'll see:** the Grid in the **Connected workspaces** list with **Enterprise Grid** and **Active** in the **Status** column.
7777
from line 156
156156
157157Claude 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.
158158
159<Warning>
160 When you disconnect a workspace, Anthropic deletes its Claude data:
161
162 * The workspace's sessions and their transcripts, including members' direct-message conversations with Claude in that workspace
163 * Its channel, workspace, and direct-message memory
164 * The routines set up in its channels, and the artifacts published from them
165 * Its scopes, with their instructions and bundle bindings
166 * The links between members' Slack and Claude accounts
167
168 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.
169</Warning>
159> [!WARNING]
160>
161> When you disconnect a workspace, Anthropic deletes its Claude data:
162>
163> * The workspace's sessions and their transcripts, including members' direct-message conversations with Claude in that workspace
164> * Its channel, workspace, and direct-message memory
165> * The routines set up in its channels, and the artifacts published from them
166> * Its scopes, with their instructions and bundle bindings
167> * The links between members' Slack and Claude accounts
168>
169> 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.
170170
171171Bundles belong to your organization, not to a workspace, so they stay available to add to other workspaces and channels; only their bindings to the deleted workspace and its channels go.
172172
No line in this hunk matches that.