One read of Claude Documentationclaude-docs-20260822T173718Z
5 pages moved out of 216 read.
Pages moved
5
significant first
Pages read
216
in this capture
Captured
17:37 UTC
Corpus hash
7fcad93ce80e
corpus-hash
What this read moved
1-5 of 5claude-tag/admins/troubleshooting Changed · +19 / -5 lines
### Using the legacy Claude in Slack bot. Ask your Claude workspace owner to enable Claude Tag.
from line 102
102102
103103**What it means**
104104
105**Allow Claude to respond to guests** is set to **Restrict** or **Channel only** for this channel's [scope](/docs/claude-tag/concepts/glossary#scope), so Claude checks the channel for guests before replying, and this install predates the `users:read` permission that check needs.
105**Allow Claude to work in channels with guests** is set to **Restrict** or **Channel only** for this channel's [scope](/docs/claude-tag/concepts/glossary#scope), so Claude checks the channel for guests before replying, and this install predates the `users:read` permission that check needs.
106106
107107**How to resolve**
108108
from line 142
142142
143143**What it means**
144144
145The channel includes at least one Slack guest account, and **Allow Claude to respond to guests** is set to **Restrict** for this channel's scope. **Restrict** is the default.
145The channel includes at least one Slack guest account, and **Allow Claude to work in channels with guests** is set to **Restrict** for this channel's scope. **Restrict** is the default.
146146
147147**How to resolve**
148148
from line 149
149149Either fix works:
150150
151151* Remove the guests from the channel, or move the conversation to a channel with no guests; this changes no settings, so no other channel is affected.
152* Or change **Allow Claude to respond to guests** for the scope covering this channel; changing it needs an organization owner. **Channel only** restores replies while keeping Claude to the channel's own instructions and access. **Allow** gives guests the full access the scope has. The setting is at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag), on the **Slack** tab under **Claude Tag's access**, in the scope's collapsed **Advanced** section. Either value applies to every guest channel that scope covers; to limit it to one channel, set it on the channel's own scope. See [restrict guest channels](/docs/claude-tag/admins/restrict-access#restrict-guest-channels) for what each value exposes.
152* Or change **Allow Claude to work in channels with guests** for the scope covering this channel; changing it needs an organization owner. **Channel only** restores replies while keeping Claude to the channel's own instructions and access. **Allow** gives guests the full access the scope has. The setting is at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag), on the **Slack** tab under **Claude Tag's access**, in the scope's collapsed **Advanced** section. Either value applies to every guest channel that scope covers; to limit it to one channel, set it on the channel's own scope. See [restrict guest channels](/docs/claude-tag/admins/restrict-access#restrict-guest-channels) for what each value exposes.
153153
154154Either value restores replies, not workspace search. Claude can't search the workspace from a channel that includes guests, even under **Allow**. Removing the guests restores search as well.
155155
from line 170
170170**How to resolve**
171171
1721721. Mention Claude again; the retry usually clears it.
1732. If one channel hits this repeatedly, the membership check may be failing on an unusually large channel. Setting **Allow Claude to respond to guests** to **Allow** on the channel's scope removes the guest check for every channel that scope covers, which usually stops the message from recurring; weigh [what Allow exposes](#claude-doesn%E2%80%99t-respond-in-channels-that-include-guests) first.
1732. If one channel hits this repeatedly, the membership check may be failing on an unusually large channel. Setting **Allow Claude to work in channels with guests** to **Allow** on the channel's scope removes the guest check for every channel that scope covers, which usually stops the message from recurring; weigh [what Allow exposes](#claude-doesn%E2%80%99t-respond-in-channels-that-include-guests) first.
174174
175175### This channel is shared across multiple workspaces
176176
from line 184
184184
185185**What it means**
186186
187This message comes from the guest check, not from workspace sharing. **Allow Claude to respond to guests** is set to **Restrict** or **Channel only** for this channel's scope, and the channel's membership can't be verified, most often because the channel is shared across an Enterprise Grid organization, so Claude declines.
187This message comes from the guest check, not from workspace sharing. **Allow Claude to work in channels with guests** is set to **Restrict** or **Channel only** for this channel's scope, and the channel's membership can't be verified, most often because the channel is shared across an Enterprise Grid organization, so Claude declines.
188188
189189**How to resolve**
190190
from line 355
355355**How to resolve**
356356
357357Run [the pairing flow](/docs/claude-tag/admins/pair-workspace). If the fix worked, a mention in the workspace gets a reply.
358
359### Using the legacy Claude in Slack bot. Ask your Claude workspace owner to enable Claude Tag.
360
361**What you see**
362
363Claude posts "Using the legacy Claude in Slack bot. Ask your Claude workspace owner to enable Claude Tag." as a short notice in the thread just before its first reply.
364
365**What it means**
366
367The earlier per-user Claude in Slack app answered the message instead of the new version. That happens when the Slack workspace isn't paired with a Claude organization that has Claude Tag turned on, or when the channel's or workspace's **Claude Tag version** is set to **Legacy**. Turning Claude Tag on needs an Owner of your Claude organization, not a Slack workspace owner.
368
369**How to resolve**
370
371The fix is in claude.ai admin settings, not in Slack. An Owner turns Claude Tag on at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag) and [pairs the workspace](/docs/claude-tag/admins/pair-workspace). If the workspace is already paired, check the **Claude Tag version** on the channel's scope, then on its workspace's, and set it to **New** or **Inherit**; see [Migrate from the earlier Claude in Slack](/docs/claude-tag/admins/migrate-from-earlier). Once Claude Tag is on and the workspace is paired, the notice stops appearing.
358372
359373### Claude Tag is turned off for your organization
360374
claude-tag/concepts/for-claude-code-users Changed · +11 / -0 lines
## Claude Tag versus a bot you build on the API
from line 81
8181
8282See [What Claude remembers](/docs/claude-tag/users/memory) for how memory is scoped and how to correct it.
8383
84## Claude Tag versus a bot you build on the API
85
86A Slack bot you build on the Claude API is software your team writes and hosts. It calls the API with your key, holds its own Slack tokens, and has the tools and memory you code into it.
87
88Claude Tag is Anthropic's hosted Slack app. It takes care of the parts you would otherwise build.
89
90* **Hosting.** Each thread gets a Claude Code session in a sandbox Anthropic runs, or in the [environment](/docs/claude-tag/concepts/glossary#environment) your organization pins, under an [agent identity](/docs/claude-tag/concepts/agent-identity) of its own.
91* **Credentials.** An admin gives Claude [connections](/docs/claude-tag/admins/add-connections) to your tools, and [Agent Proxy](/docs/claude-tag/concepts/agent-identity#agent-proxy) attaches the credentials at the network boundary, outside the sandbox.
92* **Customization.** [Custom instructions](/docs/claude-tag/admins/attach-to-scope#add-custom-instructions), [channel memory](/docs/claude-tag/users/memory), and [routines](/docs/claude-tag/users/proactivity) are built in.
93* **Governance and billing.** [Access controls](/docs/claude-tag/admins/restrict-access) and spend limits are set in claude.ai admin settings, and usage is [billed to the organization's usage balance](/docs/claude-tag/overview#billing-and-spend-limits).
94
8495## Related resources
8596
8697* [How Claude Tag works](/docs/claude-tag/concepts/how-it-works): the session model this page maps your setup onto
claude-tag/users/proactivity Changed · +4 / -2 lines
from line 32
3232
3333### Follow a pull request
3434
35Claude can subscribe to a single pull request and react when it updates.
35Claude can subscribe to a single pull request and react when it updates. A subscription is the one way Claude reacts to GitHub events; it wakes on activity on that pull request, such as a comment, a failed check, or a merge. You can't set up a routine from Slack that fires on other repository events, such as every new pull request.
3636
3737```text wrap theme={null}
3838@Claude subscribe to PR #482 in acme/data-pipeline. When CI finishes or a review lands, post here, and tag me if anything failed.
from line 100
100100* **Edit.** Describe the change and it updates the job
101101* **Disable.** Name the job to stop, as in "disable the Friday rollup"
102102
103Standing work is visible to the channel: jobs post into the channel they belong to. Routines keep running if their creator leaves the organization, but stop firing if the creator is removed from the channel.
103Standing work is visible to the channel: jobs post into the channel they belong to, or into another public channel you name that Claude has been added to. Routines keep running if their creator leaves the organization, but stop firing if the creator is removed from the channel.
104104
105105A few boundaries apply:
106106
107107* A job runs with the channel's connections, the same as an interactive request.
108* Claude can post a job's output into another public channel in the same workspace only if the job's own channel is public and Claude has been added to the target channel. It labels the message with the channel it came from.
109* Claude doesn't post job output to private channels, DMs, group DMs, or externally shared channels, and doesn't message people directly. The one exception is the completion or failure notice it sends to whoever set up the routine, and only when that person's Slack account is connected to their Claude account.
108110* Schedules default to UTC. When you say "every weekday at 9am," include the timezone (for example "9am Pacific") so Claude converts correctly; without one it may guess. Ask "what triggers do you have set up?" to confirm the time it actually scheduled.
109111* A scheduled job that touches a github.com repository uses the same GitHub connection your admin set up for interactive work. See [Configure GitHub access](/docs/claude-tag/admins/configure-github#scheduled-work-uses-the-same-connection).
110112
claude-tag/admins/restrict-access Changed · +2 / -2 lines
from line 95
9595DMs, guest channels, and shared channels sit outside the version setting:
9696
9797* **DMs.** The version setting doesn't cover them. To close those off too, turn off [Allow direct messages](#allow-or-disable-direct-messages).
98* **Guest channels.** By default Claude is off in any channel that includes a Slack guest. If a chosen channel has guests, also set [Allow Claude to respond to guests](#restrict-guest-channels) to **Allow** or **Channel only** on its scope.
98* **Guest channels.** By default Claude is off in any channel that includes a Slack guest. If a chosen channel has guests, also set [Allow Claude to work in channels with guests](#restrict-guest-channels) to **Allow** or **Channel only** on its scope.
9999* **Shared channels.** A [channel shared across workspaces in your Enterprise Grid](#channels-shared-across-workspaces-in-your-enterprise-grid) takes its settings from **Default Slack access** only, and Claude [doesn't operate in Slack Connect channels](#externally-shared-channels) at all; neither can serve as a chosen channel.
100100
101101To control who can use Claude in the allowed channels, turn on the [restriction toggle](#restrict-who-can-use-claude); to cap what a channel spends, [set a per-channel spend limit](#set-spend-limits).
from line 113
113113
114114### Restrict guest channels
115115
116By default, Claude is disabled in any channel that includes a Slack guest. The **Allow Claude to respond to guests** setting changes that per scope. It's at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag), on the **Slack** tab under **Claude Tag's access**, in the scope's collapsed **Advanced** section, and it has three values:
116By default, Claude is disabled in any channel that includes a Slack guest. The **Allow Claude to work in channels with guests** setting changes that per scope. It's at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag), on the **Slack** tab under **Claude Tag's access**, in the scope's collapsed **Advanced** section, and it has three values:
117117
118118| Value | What Claude does in a channel that includes a guest |
119119| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
claude-tag/admins/setup-overview Changed · +2 / -0 lines
from line 112
112112
113113See [Give Claude access](/docs/claude-tag/admins/add-connections) for how to create the accounts and what access to give them.
114114
115You can use any address. The setup flow shows `claude@` followed by your own domain only as an example; Claude Tag never asks for the address and keeps only the credential you enter for each tool.
116
115117### Launch Claude Tag
116118
117119Channel work draws from your organization's usage balance, not from individual seats; the spend limit you set here caps how much of that balance Claude Tag can use each billing period. (DMs run on the user's own claude.ai account and aren't capped by this limit.)