Manage workspaces and versions changedclaude-tag/admins/workspaces
Nearest release: v2.1.290, published under 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 5 Oct 2026 18:53 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 5 Oct 2026 19:07 UTC.
Upstream edited
Recorded here
Lines+49added
Lines−20removed
From line
16
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits20to this page, all time
### What each Claude Tag switch turns off
The whole hunk
from line 16, old and new numbered
/
from line 16
1616
1717A Slack workspace or Enterprise Grid pairs with one Claude organization at a time.
1818
19To move a pairing to a different Claude organization, an Owner in the organization that currently holds it must [disconnect it](#revoke-a-pairing) first. Until then, the console refuses the new pairing as [already connected to a different organization](/docs/claude-tag/admins/troubleshooting#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.
19To move a pairing to a different Claude organization, an Owner in the organization that currently holds it must [disconnect it](#revoke-a-pairing) first. Until then, Claude Tag refuses the new pairing as [already connected to a different organization](/docs/claude-tag/admins/troubleshooting#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.
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
2323<Steps>
2424 <Step title="Open the pairing dialog">
25 At [`claude.ai/admin-settings/claude-tag`](https://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**.
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 a workspace**.
2626 </Step>
2727
2828 <Step title="Get a pairing code from Slack">
from line 30
3030
3131 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).
3232 </Step>
33
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>
3337</Steps>
3438
3539<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>
3640
37**You'll see:** the new workspace in the Slack row's connected list and as a scope in the **Claude Tag's access** section.
41**You'll see:** the new workspace in the **Connected workspaces** list with the status **Active**, and as a row on the **Channels** tab.
3842
3943## Set up Claude Tag on Enterprise Grid
4044
from line 69
6569Paste the `enterprise_` code in one of these places:
6670
6771* **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)
68* **After setup:** go to [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag) > **Where Claude Tag works** > the Slack row's **⋮** menu > **+ Add workspace**, and paste the code into the dialog
72* **After setup:** click **Connect a workspace** under **Connected workspaces** on the **Slack** page, as in [Pair another workspace](#pair-another-workspace), and paste the code into the dialog. The Grid's row in the list shows **Enterprise Grid**.
6973
7074Claude 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.
7175
from line 77
7377
7478## Turn Claude Tag on or off and set the version for a scope
7579
76Each 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](#turn-claude-tag-on-or-off-on-the-team-plan) replaces them. Both controls are on the scope's panel at [`claude.ai/admin-settings/claude-tag`](https://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.
80Each workspace and channel has its own page with two controls: an enable switch that turns Claude on or off there, and a **Claude Tag version** setting that chooses which version answers while it's on. On the Team plan, a [single switch on the **Slack** page](#turn-claude-tag-on-or-off-on-the-team-plan) replaces them. To open a workspace's or channel's page, go to [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag), open the **Channels** tab under **Claude's access**, and select the workspace or channel. To find a channel, search for it by name.
7781
78The **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.
82The enable switch, **Enable Claude Tag in this workspace** or **Enable Claude Tag in this channel**, sits at the top of the page's **General** tab. While the switch is off, Claude doesn't respond to @-mentions there. One-to-one direct messages from members who have connected a Claude account are unaffected. Turning the switch on routes the workspace or channel to **New**. To make it follow its parent again, click **Use inherited setting** under the switch.
7983
80The **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.
84The **Claude Tag version** setting is on the page's **Advanced** tab and is unavailable while Claude Tag is off there. Choosing **Inherit** clears the workspace's or channel's own setting entirely, so it also follows its parent for on or off.
8185
8286| Label | Effect |
8387| :- | :- |
84| **New** | Claude Tag. Access bundles, skills, and custom instructions apply |
88| **New** | Claude Tag. Bundles, skills, and custom instructions apply |
8589| **Legacy** | The earlier per-user Claude in Slack. Bundles and skills do not apply. Being deprecated; see [Migrate from the earlier app](/docs/claude-tag/admins/migrate-from-earlier) |
86| **Inherit** | Use the parent scope's value. Not shown at **Default Slack access** |
90| **Inherit** | Use the parent's value. Not shown on the **Slack** page |
8791
88Both 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**.
92Turning off **Respond in all channels** doesn't stop Claude in a workspace or channel whose own enable switch is on. On the Enterprise plan, launching setup for a single workspace turns on that workspace's enable switch, so Claude keeps responding in that workspace. The switch is at the top of the **General** tab on the **Slack** page, which sets the default for every workspace and channel. Direct messages from members who have connected a Claude account are unaffected.
8993
94Both versions answer through the same @Claude app, so turning off a workspace's or channel's enable switch silences the Legacy version there too. To opt out of Claude Tag while keeping the earlier behavior, leave the switch on and set **Claude Tag version** to **Legacy**.
95
9096Per-scope version changes (workspace and channel) are reversible; see [Migrate from the earlier app](/docs/claude-tag/admins/migrate-from-earlier).
9197
98### What each Claude Tag switch turns off
99
100Each of these switches turns Claude off in a different part of Slack. To stop only direct messages, see [Allow or disable direct messages](/docs/claude-tag/admins/restrict-access#allow-or-disable-direct-messages).
101
102| Switch | Where it is | When it's off |
103| :- | :- | :- |
104| **Enable Claude Tag in Slack** | The top of [Claude Tag admin settings](https://claude.ai/admin-settings/claude-tag) | Claude is off in every channel and in direct messages |
105| **Respond in all channels** | The top of the **General** tab on the [**Slack** page](https://claude.ai/admin-settings/claude-tag/channels/slack) | Claude is off in channels, except where the channel's or its workspace's own enable switch is on |
106| **Respond in channels** | The same place as **Respond in all channels**, [on the Team plan](#turn-claude-tag-on-or-off-on-the-team-plan) | Claude is off in the channels of every connected workspace |
107| **Enable Claude Tag in this workspace** | The top of the **General** tab on the workspace's page | Claude is off in that workspace's channels, except a channel whose own enable switch is on |
108| **Enable Claude Tag in this channel** | The top of the **General** tab on the channel's page | Claude is off in that channel |
109
92110## Turn Claude Tag on or off on the Team plan
93111
94On the [Team plan](https://claude.com/pricing), you turn Claude on or off in every connected Slack workspace with one switch, at [`claude.ai/admin-settings/claude-tag`](https://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-tag-on-or-off-and-set-the-version-for-a-scope).
112On the [Team plan](https://claude.com/pricing), one switch turns Claude on or off in the channels of every connected Slack workspace: **Respond in channels**, at the top of the **General** tab at [**Claude's access > Channels > Slack**](https://claude.ai/admin-settings/claude-tag/channels/slack). The switch doesn't override a workspace that was turned off on its own.
95113
114On the Enterprise plan, and in a Team organization whose Slack configuration can't be expressed as one on-or-off choice, the **Slack** page shows **Respond in all channels** instead, and each workspace and channel page has its own enable switch and **Claude Tag version** setting. A Team organization gets those controls when any of these is true:
115
116* The **Slack** page, a workspace, or a channel is set to **Legacy**
117* A workspace or channel is set to **New** on its own page
118* A channel is switched off on its own page
119* A bundle or connector is added directly to a channel
120
121For those controls, see [Turn Claude Tag on or off and set the version for a scope](#turn-claude-tag-on-or-off-and-set-the-version-for-a-scope).
122
96123### Turn Claude off in channels
97124
98Go to [`claude.ai/admin-settings/claude-tag`](https://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**](/docs/claude-tag/admins/restrict-access#allow-or-disable-direct-messages) toggle. For members who haven't connected an account, see [Stop direct messages from members without a Claude account](/docs/claude-tag/admins/restrict-access#stop-direct-messages-from-members-without-a-claude-account).
125Turn off **Respond in channels** on the **Slack** page. 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, go to [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag), click **Edit** on the **Direct messages** row, and turn off [**Allow direct messages**](/docs/claude-tag/admins/restrict-access#allow-or-disable-direct-messages). For members who haven't connected an account, see [Stop direct messages from members without a Claude account](/docs/claude-tag/admins/restrict-access#stop-direct-messages-from-members-without-a-claude-account).
99126
100127### Turn Claude back on
101128
102Go to [`claude.ai/admin-settings/claude-tag`](https://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](/docs/claude-tag/admins/attach-to-scope) and [custom instructions](/docs/claude-tag/admins/attach-to-scope#add-custom-instructions), applies again. A workspace that was turned off on its own stays off, along with its channels.
129Turn on **Respond in channels** on the **Slack** page. Everything you set on the **Slack** page and on each workspace's and channel's page, such as [bundles](/docs/claude-tag/admins/attach-to-scope) and [custom instructions](/docs/claude-tag/admins/attach-to-scope#add-custom-instructions), applies again. A workspace that was turned off on its own stays off, along with its channels.
103130
104131### Turn Claude off for the whole organization
105132
106Go to [`claude.ai/admin-settings/claude-tag`](https://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.
133Go to [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag) and turn off the **Enable Claude Tag in Slack** switch at the top of the page. That switch turns off direct messages too.
107134
108135### Keep Claude out of specific channels
109136
from line 138
111138
112139### Notices that settings aren't applied
113140
114When a workspace or channel entry shows a notice that its settings aren't applied, nothing you set there is lost.
141When a workspace's or channel's page shows a notice that its settings aren't applied, nothing you set there is lost.
115142
116143| Notice | What to do |
117144| :- | :- |
118| "These settings aren't applied while Claude Tag is disabled. They're saved and will take effect once it's enabled." | Go to [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag) → **Claude Tag's access** → **Slack** → **Default Slack** → **Enable Claude Tag** and turn the switch on |
145| "These settings aren't applied while Claude Tag is disabled. They're saved and will take effect once it's enabled." | Turn on **Respond in channels** on the **Slack** page |
119146| "These settings aren't applied while Claude Tag is turned off for this workspace or channel; the org-wide Enable Claude Tag setting doesn't override that. They're saved and will take effect once it's turned back on." | The workspace, or the channel's workspace, was turned off on its own, and the switch doesn't override that. While you have the single switch, the admin page has no control for that workspace setting |
120| "These settings aren’t applied while Claude Tag setup is incomplete for this workspace or channel." | Select the **Resume** *workspace* **setup** button beside the notice and finish that workspace's setup. On a channel's entry, the button's label names the channel's workspace |
147| "These settings aren’t applied while Claude Tag setup is incomplete for this workspace or channel." | Select the **Resume** *workspace* **setup** button beside the notice and finish that workspace's setup. On a channel's page, the button's label names the channel's workspace |
121148
122149## Revoke a pairing
123150
124In 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.
151Go to [**Claude's access > Channels > Slack**](https://claude.ai/admin-settings/claude-tag/channels/slack). Under **Connected workspaces** on the **General** tab, click **Disconnect** on the workspace's row, type the workspace's name to confirm, and click **Disconnect**. While **Enable Claude Tag in Slack** is off, the same list appears under **Claude Tag in Slack** in Claude Tag admin settings.
125152
153Claude 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.
154
126155<Warning>
127156 When you disconnect a workspace, Anthropic deletes its Claude data:
128157
from line 164
135164 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.
136165</Warning>
137166
138Access 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.
167Bundles 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.
139168
140After 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`.
169After you disconnect, the workspace leaves the **Connected workspaces** list. If it was your only connected workspace, the top of Claude Tag admin settings shows that it was disconnected from Slack, with a **Reconnect** button. **Reconnect** reopens the pairing dialog, where you redeem a fresh code from `@Claude connect`.
141170
142171The 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](/docs/claude-tag/admins/restrict-access#quiet-or-remove-claude-tag).
143172
No line in this hunk matches that.