One read of Claude Documentationclaude-docs-20261005T190707Z
56 pages moved out of 261 read.
Pages moved
56
significant first
Pages read
261
in this capture
Captured
19:07 UTC
Corpus hash
67472caaae39
corpus-hash
What this read moved
51-56 of 56, page 3 of 3This capture is too large to show at once. Changes 51-56 of 56 are below, significant first; the rest are on the following screens.
claude-tag/users/when-claude-responds Changed · +11 / -9 lines
from line 39
3939
4040## Turn automatic replies on or off
4141
42The **Respond automatically** setting controls whether Claude replies to a channel's messages without an @-mention. When it's on, Claude may reply to a message it judges warrants one, as [What Claude does with a channel message](#what-claude-does-with-a-channel-message) describes. When it's off, Claude replies in that channel only when someone @-mentions it.
42The **Respond automatically** setting controls whether Claude replies to a channel's messages without an @-mention. When it's on, Claude may reply to a message it judges warrants one, as [What Claude does with a channel message](#what-claude-does-with-a-channel-message) describes. When it's off, Claude replies in that channel only when someone @-mentions it. The setting is on by default.
4343
44The setting is on by default.
45
4644Each channel has its own copy of the setting, and there is no workspace- or organization-wide version. To make Claude mention-only across many channels, turn it off in each one.
4745
4846All three places below change the same setting, so a change you make in one appears in the others.
from line 48
5048| Where | How |
5149| :- | :- |
5250| In Slack | Ask Claude in the channel, for example "@Claude only respond in this channel when someone @-mentions you" or "@Claude respond to messages here even when nobody mentions you." Claude confirms the change. |
53| The channel's Configure page | Open the **Configure** link in the footer of any Claude reply in the channel and switch the **Respond automatically** toggle. See [Configure Claude for a channel](/docs/claude-tag/users/good-habits#configure-claude-for-a-channel). |
54| The Claude Tag admin page (admins only) | At [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag), on the **Slack** tab under **Claude Tag's access**, open the channel's scope and switch **Respond automatically** in its **Advanced** settings. |
51| The channel's Configure page | Open the **Configure** link in the footer of any Claude reply in the channel, switch the **Respond automatically** toggle, and click **Save**. See [Configure Claude for a channel](/docs/claude-tag/users/good-habits#configure-claude-for-a-channel). |
52| Claude Tag admin settings (Owners and Claude Tag admins) | Go to [**Organization settings > Claude Tag**](https://claude.ai/admin-settings/claude-tag?access=channels), select the channel on the **Channels** tab, and switch **Respond automatically** on the channel's **General** tab. |
5553
56When the scope's [**Channel member edits**](/docs/claude-tag/admins/attach-to-scope#restrict-who-can-set-channel-instructions) setting is **Block**, Claude declines to change **Respond automatically** when anyone asks in Slack, and channel members can't switch the toggle on the channel's Configure page. An admin can still change the setting on the Claude Tag admin page, and a [channel manager](/docs/claude-tag/admins/restrict-access#delegate-channel-setup-to-channel-managers) can still switch the toggle on the Configure page of a channel assigned to them.
54An Owner or a [Claude Tag admin](/docs/claude-tag/admins/restrict-access#delegate-claude-tag-administration) can set [**Channel member edits**](/docs/claude-tag/admins/attach-to-scope#restrict-who-can-set-channel-instructions) to **Block** for a channel, a workspace, or all of Slack. When the setting is **Block**, Claude declines to change **Respond automatically** when anyone asks in Slack, and channel members can't switch the toggle on the channel's Configure page. An Owner or a Claude Tag admin can still change the setting in Claude Tag admin settings, and a [channel manager](/docs/claude-tag/admins/restrict-access#delegate-channel-setup-to-channel-managers) can still switch the toggle on the Configure page of a channel assigned to them.
5755
5856The setting covers the channel's messages, not DMs. To quiet a single thread instead of the whole channel, [ask Claude in that thread](#quiet-one-conversation).
5957
60Until Claude has joined a channel, you see "@-mention Claude in this channel to activate" in place of the toggle on the Configure page and the admin page. You see the same line in a channel shared across workspaces that all belong to your Claude organization, because Claude runs there with your organization's default settings only. [Messages that never get a reply](#messages-that-never-get-a-reply) covers shared channels in more detail.
58Until Claude has joined a channel, you see "@-mention Claude in this channel to activate" in place of the toggle, both on the Configure page and on the channel's page in Claude Tag admin settings. You see the same line in a channel shared across workspaces that all belong to your Claude organization, because Claude runs there with your organization's default settings only. [Messages that never get a reply](#messages-that-never-get-a-reply) covers shared channels in more detail.
6159
60<Note>
61 Separately from **Respond automatically**, an Owner or a Claude Tag admin can [turn Claude off in channels](/docs/claude-tag/admins/workspaces#turn-claude-tag-on-or-off-and-set-the-version-for-a-scope).
62</Note>
63
6264## Messages from other apps and bots
6365
6466Claude reads a message that another Slack app or bot posts as channel context, and replies to it only when the message includes `@Claude`. Claude treats alerts an integration posts, messages a Slack workflow posts, and messages from any other bot the same way.
from line 103
101103@Claude only respond in this channel when someone @-mentions you directly.
102104```
103105
104Claude confirms the change, which is channel-wide, not just for you. You can make the same change with the toggle on the channel's Configure page, and an admin can make it from the Claude Tag admin page. If Claude declines because an admin has locked the channel's settings, ask an admin to make the change from the Claude Tag admin page, as [Turn automatic replies on or off](#turn-automatic-replies-on-or-off) describes.
106Claude confirms the change, which is channel-wide, not just for you. You can make the same change with the toggle on the channel's Configure page, and an Owner or a [Claude Tag admin](/docs/claude-tag/admins/restrict-access#delegate-claude-tag-administration) can change it in [Claude Tag admin settings](https://claude.ai/admin-settings/claude-tag). If Claude declines because an Owner or a Claude Tag admin has locked the channel's settings, ask one of them to make the change in Claude Tag admin settings, as [Turn automatic replies on or off](#turn-automatic-replies-on-or-off) describes.
105107
106108Threads Claude already joined keep forwarding replies, so quiet those individually with the in-thread line above. The [`!mute` command](/docs/claude-tag/users/commands#mute-or-unmute-a-thread) quiets one thread at a time and does nothing at a channel's top level.
107109
from line 135
133135A few cases produce silence even when the message includes a mention:
134136
135137* **Editing a message to add the mention.** An edit doesn't trigger a response. Delete the message and send a new one with `@Claude` included.
136* **Channels with guest accounts.** By default, Claude is off in channels that include guests; your admin can turn it on per scope. Ask whoever runs your Claude plan, or send them [the guest access setting](/docs/claude-tag/admins/restrict-access#restrict-guest-channels).
138* **Channels with guest accounts.** By default, Claude is off in channels that include guests; an Owner or a Claude Tag admin can turn it on for a channel, a workspace, or all of Slack. Ask whoever runs your Claude plan, or send them [the guest access setting](/docs/claude-tag/admins/restrict-access#restrict-guest-channels).
137139* **Channels shared across workspaces connected to different Claude organizations.** Every workspace where Claude runs is connected to a Claude organization, the account a company sets up for Claude. When a channel is shared across workspaces connected to different Claude organizations, Claude won't reply there and posts a refusal message instead. You can't tell from Slack how a workspace is connected; the refusal message itself is the signal. Use a channel that belongs to one workspace, or send Claude a DM.
138140* **Slack Connect channels.** Claude doesn't answer in [channels shared with another company](/docs/claude-tag/admins/restrict-access#slack-connect-channels). A mention there gets a notice saying Claude isn't turned on for Slack Connect channels, and no admin setting changes that.
139141
claude-tag/admins/federated-access/token-reference Changed · +1 / -1 lines
from line 88
8888| `jti` | Unique token ID |
8989| `tenant` | Your Claude organization ID, the same value as the subject's `org/` segment. Together with `iss`, this is the pair a relying party pins to trust tokens from one organization. Not your cloud or identity provider's tenant ID. |
9090| `agent_id` | The agent ID, the same value as the subject's `agent/` segment |
91| `profile_id` | The ID of the Access bundle the connection belongs to, starting with `capp_`. Informational. |
91| `profile_id` | The ID of the bundle the connection belongs to, starting with `capp_`. Informational. |
9292| `platform` | `slack` when the request came from Slack. Present whenever `slack_workspace_id` is. |
9393| `slack_workspace_id` | The ID of the Slack workspace Claude is acting in. Present when the request came from a Slack workspace your organization owns. |
9494| `slack_channel_id` | The ID of the Slack channel Claude is acting in. Present whenever `slack_workspace_id` is and Claude is acting in one channel rather than a whole workspace. |
claude-tag/users/commands Changed · +1 / -1 lines
from line 24
2424@Claude !configure
2525```
2626
27Run `!configure` in a channel, and Claude replies in the thread with a link to that channel's Configure page on claude.ai. On that page you [tailor how Claude works in the channel](/docs/claude-tag/users/good-habits#configure-claude-for-a-channel), for example by editing its channel instructions, and it's the same page the **Configure** link in the footer of any Claude reply opens. In a DM with Claude there are no per-channel settings, so Claude replies there with a link to the [Claude Tag admin page](https://claude.ai/admin-settings/claude-tag) instead.
27Run `!configure` in a channel, and Claude replies in the thread with a link to that channel's Configure page on claude.ai. On that page you [tailor how Claude works in the channel](/docs/claude-tag/users/good-habits#configure-claude-for-a-channel), for example by editing its channel instructions, and it's the same page the **Configure** link in the footer of any Claude reply opens. In a DM with Claude there are no per-channel settings, so Claude replies there with a link to [Claude Tag admin settings](https://claude.ai/admin-settings/claude-tag) instead.
2828
2929## Restart a stuck or wrong-context session
3030
claude-tag/users/memory Changed · +2 / -2 lines
from line 30
3030
3131Other workspaces stay separate. One-to-one direct messages stay separate too. Claude keeps notes for each one-to-one direct-message conversation, stored with the workspace rather than with your Claude account. Those notes are deleted when an Owner [disconnects the workspace](/docs/claude-tag/admins/workspaces#revoke-a-pairing), not when you disconnect your own Claude account in Slack.
3232
33If a channel switches between public and private, its channel notes stay with the channel, and Claude keeps reading and adding to them there. Workspace notes Claude saved from the channel while it was public stay in the workspace notes. If those shouldn't stay shared, ask an Owner to delete them from the workspace scope's memory files.
33If a channel switches between public and private, its channel notes stay with the channel, and Claude keeps reading and adding to them there. Workspace notes Claude saved from the channel while it was public stay in the workspace notes. If those shouldn't stay shared, ask an Owner to delete them from the workspace's memory files in [Claude Tag admin settings](https://claude.ai/admin-settings/claude-tag).
3434
3535## Manage what Claude Tag remembers
3636
from line 63
6363* **After correcting an entry, have Claude record the fix.** "Update your memory for this channel so this doesn't happen again" turns a one-time fix into a standing one.
6464* **Prune what your work has outgrown.** Entries written weeks ago can describe a repository, owner, or convention that no longer exists. Ask Claude in the channel to review its memory and drop the entries that no longer apply. For ongoing upkeep, set up a [routine](/docs/claude-tag/users/proactivity) that repeats the review on a schedule; weekly works well.
6565
66An Owner in your Claude organization can view, edit, or delete a scope's memory files at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag), under the scope's options menu.
66An Owner in your Claude organization can view, edit, or delete the [memory files](/docs/claude-tag/admins/audit) of a workspace and its channels.
6767
6868## Related resources
6969
claude-tag/users/models Changed · +2 / -2 lines
from line 34
3434@Claude use Sonnet for this thread, and make it the default model for this channel.
3535```
3636
37Claude sets the channel's default model. New threads in the channel start on it. If you asked for a family rather than a version, the default keeps following that family: when your organization gets a newer model in it, new threads start on the newer model without anyone changing the setting. A thread already underway switches to it at the next message anyone posts there, unless someone in that thread has already had Claude switch models. If an admin has set the scope's **Channel member edits** setting to **Block**, Claude declines to set the channel default; ask for the thread alone instead.
37Claude sets the channel's default model. New threads in the channel start on it. If you asked for a family rather than a version, the default keeps following that family: when your organization gets a newer model in it, new threads start on the newer model without anyone changing the setting. A thread already underway switches to it at the next message anyone posts there, unless someone in that thread has already had Claude switch models. If an Owner or a [Claude Tag admin](/docs/claude-tag/admins/restrict-access#delegate-claude-tag-administration) has set **Channel member edits** to **Block** for the channel, Claude declines to set the channel default; ask for the thread alone instead.
3838
39Admins set the same default from claude.ai, per workspace or channel; see [choose the model for a scope](/docs/claude-tag/admins/customize#choose-the-model-for-a-scope).
39An Owner sets the same default in Claude Tag admin settings for the whole organization or for one workspace or channel, and a Claude Tag admin can set it for a workspace or channel; see [choose the model for a scope](/docs/claude-tag/admins/customize#choose-the-model-for-a-scope).
4040
4141## Choose the model for your direct messages
4242
claude-tag/users/troubleshooting Changed · +1 / -1 lines
from line 683
683683
684684**How to resolve**
685685
686Use a channel instead, or ask your admin about enabling DMs.
686Use a channel instead, or ask an Owner of your Claude organization to [turn DMs back on](/docs/claude-tag/admins/restrict-access#allow-or-disable-direct-messages).
687687
688688### Group DMs aren't supported yet
689689