One read of Claude Documentationclaude-docs-20261103T223710Z
9 pages moved out of 281 read.
Pages moved
9
significant first
Pages read
281
in this capture
Captured
22:37 UTC
Corpus hash
347190df674e
corpus-hash
What this read moved
1-9 of 9claude-tag/users/troubleshooting Changed · +4 / -4 lines
from line 213
213213
214214**What it means**
215215
216The channel's [**Respond automatically**](https://claude.com/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off) setting is on. The setting is on by default.
216The channel's [**How Claude participates**](https://claude.com/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off) setting lets Claude reply without an @-mention. **Respond automatically** is the default.
217217
218218In a channel where someone has [told Claude which kinds of untagged messages to answer](https://claude.com/docs/claude-tag/users/when-claude-responds.md#what-claude-does-with-a-channel-message), it answers those kinds as well.
219219
220220**How to resolve**
221221
222Turn the **Respond automatically** setting off in the channel where the replies are appearing.
222Set **How Claude participates** to **Only when @-mentioned** in the channel where the replies are appearing.
223223
224224Post `@Claude only respond in this channel when someone @-mentions you` at the channel's top level, not in a thread. Claude confirms the change, which applies to the whole channel rather than to you alone.
225225
226If Claude doesn't confirm the change, turn the setting off on the channel's Configure page:
226If Claude doesn't confirm the change, use the channel's Configure page:
227227
2282281. Open the **Configure** link in the footer of any Claude reply in the channel.
2292292. Turn off the **Respond automatically** toggle.
from line 231
231231
232232If the Configure page says an admin has locked the channel's settings, ask an admin to [turn automatic replies off](https://claude.com/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off) for the channel.
233233
234The **Respond automatically** setting doesn't quiet a thread Claude has already posted in. To quiet one of those threads, reply in it with an instruction such as "only respond when I @-mention you".
234To quiet a thread Claude has already posted in, reply in it with an instruction such as "only respond when I @-mention you".
235235
236236### I want to take back something I sent
237237
claude-tag/users/when-claude-responds Changed · +20 / -13 lines
from line 16
1616| :- | :- |
1717| A one-to-one DM with Claude | Always. Every message is addressed to Claude already |
1818| A thread Claude is already in | Yes, unless you've [quieted the thread](#quiet-one-conversation). Once Claude has joined, every reply there reaches it without another mention |
19| A channel, top-level | Sometimes. [What Claude does with a channel message](#what-claude-does-with-a-channel-message) describes how it decides. Include `@Claude` to guarantee a reply, or [turn unprompted replies off](#quiet-the-whole-channel) |
19| A channel, top-level | Sometimes, under the default [**How Claude participates**](#turn-automatic-replies-on-or-off) setting. [What Claude does with a channel message](#what-claude-does-with-a-channel-message) describes how it decides. Include `@Claude` to guarantee a reply, or [turn unprompted replies off](#quiet-the-whole-channel) |
2020| A group DM that includes Claude, top-level | Sometimes. See [When Claude replies in a group DM](https://claude.com/docs/claude-tag/users/group-dms.md#when-claude-replies-in-a-group-dm) |
2121| A message another app or bot posted | No. Claude reads it as context. To get a reply, have the app include `@Claude` in its message. [Messages from other apps and bots](#messages-from-other-apps-and-bots) covers when that mention goes unanswered |
2222
from line 28
2828
2929## What Claude does with a channel message
3030
31Claude reads every top-level message in a channel it belongs to, and the replies in the channel's threads, whether or not anyone tagged it. For each message, it decides what to do from the channel's recent messages, the channel's [memory](https://claude.com/docs/claude-tag/users/memory.md), and any instructions your admin has set or a channel member has asked it to remember, and does one of five things.
31Under the default [**Respond automatically**](#turn-automatic-replies-on-or-off) option, Claude reads top-level messages and thread replies in a channel it belongs to, whether anyone tagged it or not, and it can [stop reading the channel](#when-claude-stops-reading-a-channel). For each message, it decides what to do from the channel's recent messages, the channel's [memory](https://claude.com/docs/claude-tag/users/memory.md), and any instructions your admin has set or a channel member has asked it to remember, and does one of these things.
3232
3333* **Nothing.** This is the usual outcome, especially in a channel where nobody has told Claude which kinds of messages to answer.
3434* **An offer to help.** When a thread leaves a concrete next step Claude could take for someone, Claude may offer in that thread to take it. The offer is either a one-line reply everyone can see or a [private suggestion](#private-suggestions-from-claude) only that person can see.
from line 49
4949
5050## Turn automatic replies on or off
5151
52The **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.
52Each channel's **How Claude participates** setting controls when Claude replies to the channel's messages.
5353
54Each 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.
54| Option | What Claude does |
55| :- | :- |
56| **Only when @-mentioned** | Waits for a person to @-mention it. In a thread it's already part of, it can also reply without a mention |
57| **Respond automatically** (the default) | 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 |
58| **Always awake** | Replies as it does under **Respond automatically**, and [keeps reading the channel](#when-claude-stops-reading-a-channel) however quiet or busy the channel gets |
59| **Start a thread session for every top-level message** | Starts a [working session](https://claude.com/docs/claude-tag/concepts/how-it-works.md) in a thread under a workspace member's new top-level message, whether the message tags Claude or not. Some messages don't start one |
5560
61Each 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, select **Only when @-mentioned** in each one.
62
5663All three places below change the same setting, so a change you make in one appears in the others.
5764
5865| Where | How |
from line 68
6168| 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](https://claude.com/docs/claude-tag/users/good-habits.md#configure-claude-for-a-channel). |
6269| 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. |
6370
64An Owner or a [Claude Tag admin](https://claude.com/docs/claude-tag/admins/restrict-access.md#delegate-claude-tag-administration) can set [**Channel member edits**](https://claude.com/docs/claude-tag/admins/attach-to-scope.md#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](https://claude.com/docs/claude-tag/admins/restrict-access.md#delegate-channel-setup-to-channel-managers) can still switch the toggle on the Configure page of a channel assigned to them.
71An Owner or a [Claude Tag admin](https://claude.com/docs/claude-tag/admins/restrict-access.md#delegate-claude-tag-administration) can set [**Channel member edits**](https://claude.com/docs/claude-tag/admins/attach-to-scope.md#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 **How Claude participates** when anyone asks in Slack, and channel members can't change **How Claude participates** 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](https://claude.com/docs/claude-tag/admins/restrict-access.md#delegate-channel-setup-to-channel-managers) can still change it on the Configure page of a channel assigned to them.
6572
6673The 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).
6774
68Until 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.
75Until Claude has joined a channel, you see "@-mention Claude in this channel to activate" in place of the options under **How Claude participates**, 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.
6976
7077> [!NOTE]
7178>
72> Separately from **Respond automatically**, an Owner or a Claude Tag admin can [turn Claude off in channels](https://claude.com/docs/claude-tag/admins/workspaces.md#turn-claude-tag-on-or-off-and-set-the-version-for-a-scope).
79> Separately from **How Claude participates**, an Owner or a Claude Tag admin can [turn Claude off in channels](https://claude.com/docs/claude-tag/admins/workspaces.md#turn-claude-tag-on-or-off-and-set-the-version-for-a-scope).
7380
7481## Messages from other apps and bots
7582
from line 115
108115
109116### Quiet the whole channel
110117
111Turn the channel's [**Respond automatically**](#turn-automatic-replies-on-or-off) setting off, so Claude replies there only when @-mentioned. From Slack, ask Claude directly.
118Set the channel's [**How Claude participates**](#turn-automatic-replies-on-or-off) setting to **Only when @-mentioned**. From Slack, ask Claude directly.
112119
113120```text wrap theme={null}
114121@Claude only respond in this channel when someone @-mentions you directly.
115122```
116123
117Claude 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](https://claude.com/docs/claude-tag/admins/restrict-access.md#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.
124Claude confirms the change, which is channel-wide, not just for you. You can make the same change under **How Claude participates** on the channel's Configure page, and an Owner or a [Claude Tag admin](https://claude.com/docs/claude-tag/admins/restrict-access.md#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.
118125
119126Threads Claude already joined keep forwarding replies, so quiet those individually with the in-thread line above. The [`!mute` command](https://claude.com/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.
120127
from line 130
123130You can stop [private suggestions](#private-suggestions-from-claude) for yourself or for everyone in a channel.
124131
125132* **For yourself**: open the **⋯** menu on a suggestion and select **Mute for a week**. The channel's [Configure page](https://claude.com/docs/claude-tag/users/good-habits.md#configure-claude-for-a-channel) opens and mutes suggestions for you for 7 days, in every channel of your organization. Other people still get theirs. To end the mute early, select **Unmute** in the "Suggestions muted for you" bar on any channel's Configure page. A suggestion in a channel without a Configure page has no **⋯** menu, but a mute you set from another channel's suggestion covers it.
126* **For the whole channel**: set the channel to reply only when someone @-mentions Claude, as [Turn automatic replies on or off](#turn-automatic-replies-on-or-off) describes. Claude then sends no suggestions in that channel.
133* **For the whole channel**: select **Only when @-mentioned** under **How Claude participates**, as [Turn automatic replies on or off](#turn-automatic-replies-on-or-off) describes. Claude then sends no suggestions in that channel.
127134
128135### Remove Claude Tag from the channel
129136
from line 144
137144
138145## When Claude stops reading a channel
139146
140Claude stops reading a channel's messages when either of these happens:
147Under the default [**Respond automatically**](#turn-automatic-replies-on-or-off) option, unless the channel is [attached to on-call](https://claude.com/docs/claude-tag/admins/setup-oncall.md), Claude stops reading the channel's top-level messages and messages in threads it isn't part of when either of these happens:
141148
142149* **Message volume.** Claude counts the messages posted in the channel since it last posted there itself, and stops reading when the count gets high enough.
143150* **Inactivity.** When more than 10 days pass without anyone @-mentioning Claude in the channel and without Claude posting there, Claude stops reading.
from line 153
146153
147154To start Claude reading again, mention `@Claude` in the channel. A mention from a person reaches Claude in both situations, and once Claude posts its reply, it reads the channel's messages again. A mention inside another app's or bot's message starts Claude reading again only after an inactivity stop.
148155
149If unprompted replies don't come back after Claude answers a mention, the channel's [**Respond automatically**](#turn-automatic-replies-on-or-off) setting is off. Answering a mention doesn't turn the setting on, and Claude changes the setting only when a channel member asks it to, so turn it back on in one of the three places listed in that section.
156If unprompted replies don't come back after Claude answers a mention, check **How Claude participates** on the channel's [Configure page](https://claude.com/docs/claude-tag/users/good-habits.md#configure-claude-for-a-channel). Answering a mention doesn't change the setting, so if the page shows **Only when @-mentioned**, change it to **Respond automatically** in one of the three places listed in [Turn automatic replies on or off](#turn-automatic-replies-on-or-off).
150157
151158## Messages that never get a reply
152159
from line 166
159166
160167When the workspaces sharing a channel all belong to one Claude organization, Claude replies there, but with only your organization's default access and settings. The repositories, instructions, and memory set up for that channel or its workspaces don't apply, and Claude posts a notice in the thread explaining this from time to time. The guest check above still applies first where guest access is restricted.
161168
162To confirm a channel's setting, check the **Respond automatically** toggle on its [Configure page](https://claude.com/docs/claude-tag/users/good-habits.md#configure-claude-for-a-channel). To confirm an instruction Claude saved, ask `@Claude what do you remember about responding in this channel?`, and see [What Claude Tag remembers](https://claude.com/docs/claude-tag/users/memory.md) for where instructions are stored and how to change them.
169To confirm a channel's setting, check **How Claude participates** on its [Configure page](https://claude.com/docs/claude-tag/users/good-habits.md#configure-claude-for-a-channel). To confirm an instruction Claude saved, ask `@Claude what do you remember about responding in this channel?`, and see [What Claude Tag remembers](https://claude.com/docs/claude-tag/users/memory.md) for where instructions are stored and how to change them.
163170
164171## Related resources
165172
third-party/claude-desktop/data-storage Changed · +6 / -4 lines
from line 101
101101Inference credentials are handled according to how they're delivered:
102102
103103* **Managed configuration** (for example, `inferenceGatewayApiKey`, `inferenceBedrockBearerToken`): read from the OS preference store or registry at launch and held in memory. The app also writes resolved credentials to a small set of transient, owner-only files for its own session processes, described below.
104* **API keys saved in the in-app configuration window**: stored in the `configLibrary/` files, encrypted with the operating system's secure storage (Keychain on macOS, DPAPI on Windows, GNOME Keyring or KWallet on Linux). Requires Claude Desktop 4.4212.0 or later, which also encrypts a key that an earlier version saved, the next time the app launches. See [Unreadable saved API keys](#unreadable-saved-api-keys).
104* **API keys saved in the in-app configuration window**: stored in the `configLibrary/` files, encrypted with the operating system's secure storage (Keychain on macOS, DPAPI on Windows, GNOME Keyring or KWallet on Linux). Requires Claude Desktop 4.4212.0 or later, which also encrypts a key that an earlier version saved, at the next launch where secure storage is available. See [Unreadable saved API keys](#unreadable-saved-api-keys).
105105* **OAuth tokens** (in-app Google sign-in, MCP servers with `oauth: true`): stored in the application-data directory, encrypted with the operating system's secure storage (Keychain on macOS, DPAPI on Windows).
106106* **Credential-helper output**: held in memory for `inferenceCredentialHelperTtlSec` seconds, then discarded and re-fetched.
107107
from line 121
121121
122122An encrypted API key can be decrypted only through the secure storage of the OS user account that saved it, so a copy of the `configLibrary/` files alone can't be decrypted elsewhere. Where that account's secure storage moves with the user, for example in a Windows roaming profile that carries the user's DPAPI keys, the key also decrypts on the other device.
123123
124When Claude Desktop can't decrypt the key that its connection uses, it shows the banner **Claude can’t read your saved key** and doesn't start sessions. The saved file stays as it is.
124When Claude Desktop can't decrypt the key that its connection uses, it shows the banner **Claude can’t read your saved key** and doesn't start sessions. Connectors set in the same saved configuration aren't listed or started until the app can decrypt the key. The saved file stays as it is.
125125
126126Have the user enter the key again in the in-app configuration window, then restart the app, after any of these:
127127
from line 134
134134These cases call for something else:
135135
136136* **Windows profiles that don't keep the user's DPAPI keys between sign-ins**: the user has to enter the key at each sign-in, so deliver the key through managed configuration instead
137* **Secure storage that isn't available as the app launches**: a restart alone is enough. For example, this happens on Linux when the app starts at login before the keyring does, and on macOS when the user dismisses the keychain prompt.
137* **Secure storage that isn't available as the app launches**: have the user restart the app once secure storage is available. They don't need to enter the key again. For example, on Linux the app can start at login before the keyring does.
138* **A macOS keychain that the app can't access as it launches**: this happens, for example, when the user dismisses the keychain prompt. Have the user restart the app, and enter their password or click **Allow** if macOS asks. If the banner stays, have the user enter the key again.
139* **A key entered again while secure storage isn't available**: the app saves the key unencrypted and uses it after a restart. At the next launch where secure storage is available, the app encrypts the key, so a later launch without secure storage shows the banner again.
138140* **Devices with no secure storage that the app can use**, such as Linux without GNOME Keyring or KWallet: the key stays unencrypted, and the configuration window shows **This key is saved unencrypted on this computer.** under the key
139* **Tools that read or write the `configLibrary/` files**: a tool that reads the key gets the encrypted value. A tool that writes an unencrypted key still works, and the app encrypts that key the next time it launches.
141* **Tools that read or write the `configLibrary/` files**: a tool that reads the key gets the encrypted value. A tool that writes an unencrypted key still works, and the app encrypts that key at the next launch where secure storage is available.
140142
141143## Automatic deletion of idle sessions
142144
claude-tag/admins/attach-to-scope Changed · +1 / -1 lines
from line 193
193193| **Allow** | Members can edit channel instructions from the Configure link |
194194| **Block** | Members can't change channel instructions, the channel's default model, or its [**Respond automatically**](https://claude.com/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off) setting |
195195
196A chain of scopes that all inherit resolves to **Allow**. Set **Block** on a workspace's page or on the **Slack** page to lock channel instructions across every channel beneath it. A [channel manager](https://claude.com/docs/claude-tag/admins/restrict-access.md#delegate-channel-setup-to-channel-managers) can still edit instructions, change the default model, and switch the **Respond automatically** toggle from the Configure page in a channel assigned to them when **Block** is set.
196A chain of scopes that all inherit resolves to **Allow**. Set **Block** on a workspace's page or on the **Slack** page to lock channel instructions across every channel beneath it. A [channel manager](https://claude.com/docs/claude-tag/admins/restrict-access.md#delegate-channel-setup-to-channel-managers) can still edit instructions, change the default model, and change **How Claude participates** from the Configure page in a channel assigned to them when **Block** is set.
197197
198198## Verify the bundle is live
199199
claude-tag/concepts/how-it-works Changed · +1 / -1 lines
from line 234
234234
235235The channel's own session, the one that handles top-level messages outside any thread, lives longer than a thread's. Claude replaces it with a fresh one after about an hour with no activity in the channel or its threads, or when the channel's configuration has changed since the session started. Claude also replaces a session once it's about a day old, but waits until the channel and the threads it's working in have gone quiet. Channel memory and the channel's history are unaffected, so the only visible effect is that Claude no longer carries what the previous session had been working on.
236236
237Claude also stops reading a channel's top-level messages once about 100 of them have arrived since it last posted or replied there. An `@Claude` mention in the channel starts it reading again; see [When Claude stops reading a channel](https://claude.com/docs/claude-tag/users/when-claude-responds.md#when-claude-stops-reading-a-channel). These thresholds are defaults and can change, so treat the numbers as approximate.
237Under **Respond automatically**, unless the channel is [attached to on-call](https://claude.com/docs/claude-tag/admins/setup-oncall.md), Claude also stops reading a channel's top-level messages and messages in threads it isn't part of once about 100 messages have arrived since it last posted or replied there. An `@Claude` mention in the channel starts it reading again; see [When Claude stops reading a channel](https://claude.com/docs/claude-tag/users/when-claude-responds.md#when-claude-stops-reading-a-channel). These thresholds are defaults and can change, so treat the numbers as approximate.
238238
239239### Channel and workspace memory
240240
claude-tag/concepts/settings-map Changed · +1 / -1 lines
from line 42
4242
4343Every Claude reply in a channel ends with a footer, and its **Configure** link opens a claude.ai page for that channel; replies in DMs have no Configure link. You can also send [`@Claude !configure`](https://claude.com/docs/claude-tag/users/commands#get-the-link-to-configure-a-channel) in the channel, and Claude replies with a link to the same page.
4444
45Anyone in the channel who is also a member of your Claude organization can edit the **Channel instructions** field on that page, unless an admin has [restricted editing to admins](https://claude.com/docs/claude-tag/admins/attach-to-scope.md#restrict-who-can-set-channel-instructions). The page's **Respond automatically** toggle controls whether Claude replies in the channel without an @-mention; see [Turn automatic replies on or off](https://claude.com/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off).
45Anyone in the channel who is also a member of your Claude organization can edit the **Channel instructions** field on that page, unless an admin has [restricted editing to admins](https://claude.com/docs/claude-tag/admins/attach-to-scope.md#restrict-who-can-set-channel-instructions). **How Claude participates** on the page controls whether Claude replies in the channel without an @-mention. See [Turn automatic replies on or off](https://claude.com/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off).
4646
4747The page's **Tools and access** tab shows the channel's resolved connections and any allowed domains. Members can see those lists but not change them there. The same tab's **Plugins** card lists the channel's plugins, and members can add plugins there unless an admin has restricted editing to admins. A **Routines** tab lists the channel's routines with each one's schedule, status, and last run.
4848
claude-tag/users/commands Changed · +1 / -1 lines
from line 77
7777:mute: Muting works per thread — reply `@Claude !mute` (or `!unmute`) inside the thread you mean.
7878```
7979
80To quiet unprompted replies across a whole channel, turn the channel's [**Respond automatically** setting](https://claude.com/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off) off.
80To quiet unprompted replies across a whole channel, set its [**How Claude participates**](https://claude.com/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off) setting to **Only when @-mentioned**.
8181
8282Unmute the same way:
8383
claude-tag/users/good-habits Changed · +1 / -1 lines
from line 189
189189
190190The **Configure** link in the footer of any Claude reply in a channel opens a page where you tailor how Claude behaves in that channel. You can also send [`@Claude !configure`](https://claude.com/docs/claude-tag/users/commands#get-the-link-to-configure-a-channel) in the channel, and Claude replies with a link to the same page. The page is on claude.ai, so you need to be signed in to your Claude organization to edit it, and an admin can [restrict editing](https://claude.com/docs/claude-tag/admins/attach-to-scope.md#restrict-who-can-set-channel-instructions) so the page is read-only for members.
191191
192The **Respond automatically** toggle on that page controls whether Claude replies in the channel without an @-mention. See [Turn automatic replies on or off](https://claude.com/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off) for what the setting does and the other places you can change it.
192**How Claude participates** on that page controls whether Claude replies in the channel without an @-mention. See [Turn automatic replies on or off](https://claude.com/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off) for what the setting does and the other places you can change it.
193193
194194Use the **Channel instructions** field on that page to write standing guidance Claude reads in every new session in the channel: the channel's purpose, its conventions, the tone replies should take, and anything Claude should do or avoid there. Channel instructions outrank channel memory and sit alongside any instructions an admin has set for the workspace or organization. Save the field and the change applies to new sessions started in the channel.
195195
connectors/building/enterprise-managed-auth Changed · +2 / -2 lines
from line 172
172172
173173Pick the organization by the kind of assertion you're testing:
174174
175* **Claude-issued**: test this kind first, because the organization needs no single sign-on (SSO), verified domain, or identity provider, so a Team organization that you create for testing qualifies as it is. Don't use an organization that signs in to Claude through Okta, because **Claude-issued** isn't available in one that does.
175* **Claude-issued**: test this first, because the organization needs no single sign-on (SSO), verified domain, or identity provider, so a Team organization that you create for testing qualifies as it is. Don't use an organization that signs in to Claude through Okta, because **Claude-issued** isn't available in one that does.
176176* **Identity provider-issued**: use an organization that signs in to Claude through Okta. If your company's organization does, test there. Otherwise, you need an Okta org, such as an integrator org from Okta's [Integrator Free Plan](https://developer.okta.com/signup/), and a Team organization that you create. Follow [Set up single sign-on](https://support.claude.com/en/articles/13132885-set-up-single-sign-on-sso) to verify a domain for the Team organization and connect SSO, choosing Okta as the provider. In the Okta org, give yourself and each test user an address on that domain. Sign in to Claude through SSO before you run the connection test.
177177
178To test both kinds of assertion, use two organizations, because **Claude-issued** isn't available in an organization that signs in to Claude through Okta.
178To test both kinds of assertion in one organization, test **Claude-issued** first, then connect Okta single sign-on and switch the connector to **IdP-managed**. A connector set up with **Claude-issued** keeps working after you connect Okta, but once you switch it, the setup doesn't offer **Claude-issued** again unless you remove single sign-on from the organization. To test in either order, use two organizations.
179179
180180### Add your connector and run the connection test
181181