One read of Claude Documentationclaude-docs-20261002T233709Z
12 pages moved out of 260 read.
Pages moved
12
significant first
Pages read
260
in this capture
Captured
23:37 UTC
Corpus hash
fb7a3047d726
corpus-hash
What this read moved
1-12 of 12claude-tag/admins/restrict-access Changed · +3 / -5 lines
from line 242
242242
243243A group DM is a Slack direct message among several people. When members add Claude to one, Claude acts with its own [service accounts](/docs/claude-tag/concepts/agent-identity), and the work bills to your organization's [usage balance](/docs/claude-tag/admins/set-spend-limit). [Use Claude Tag in a group DM](/docs/claude-tag/users/group-dms) covers what members can do there.
244244
245Claude works in group DMs on the Team plan, and for some organizations on the Enterprise plan. No admin setting makes Claude work in group DMs for an organization. If Claude doesn't work in group DMs for your organization, it answers a top-level `@Claude` mention in a group DM with the notice ["Group DMs aren't supported yet"](/docs/claude-tag/users/troubleshooting#group-dms-aren%E2%80%99t-supported-yet).
246
247245A group DM has no [scope](/docs/claude-tag/concepts/glossary#scope) of its own, so you can't attach an [Access bundle](/docs/claude-tag/admins/attach-to-scope) to one group DM or turn Claude off in one. You control every group DM in a workspace together:
248246
249247* **Access.** Claude works with the Access bundles, instructions, and repositories on the workspace's scope and on **Default Slack access**.
from line 254
256254
257255Who is in a group DM, and how Slack shares it, can change whether Claude answers:
258256
259* **A Slack guest is in the group DM.** In a workspace outside Enterprise Grid, Claude follows the [**How should Claude work in channels with guests**](#restrict-guest-channels) value on the workspace's scope or on **Default Slack access**. Under the default, **Restrict**, Claude posts its guest notice instead of an answer. Under **Channel only**, Claude runs with [channel-only access](#how-channel-only-works) and can't set up [routines](/docs/claude-tag/users/proactivity). Under **Full access**, Claude answers.
257* **A Slack guest is in the group DM.** In a workspace outside Enterprise Grid, Claude follows the [**How should Claude work in channels with guests**](#restrict-guest-channels) value on the workspace's scope or on **Default Slack access**. Under the default, **Restrict**, Claude posts its guest notice instead of an answer. Under **Channel only**, Claude runs with [channel-only access](#how-channel-only-works). Under **Full access**, Claude answers.
260258* **Someone from another company is in the group DM, through Slack Connect.** Claude doesn't answer, and no setting changes that.
261* **Slack shares the group DM across the workspaces of an Enterprise Grid.** Claude doesn't answer, whoever is in the group DM.
259* **On Enterprise Grid, the people in the group DM share no workspace.** Claude doesn't answer.
262260
263261### Direct messages from members without a Claude account
264262
from line 477
479477* **Third-party deployment.** Claude Tag runs on Anthropic's first-party service; it isn't available through third-party deployments.
480478* **Renaming or rebranding the app.** The Claude app's name, @-handle, and avatar in Slack are fixed; there is no per-workspace rename setting.
481479* **Per-user spend caps on channel work.** Spend limits apply at the organization and channel level. There's no way to cap what one member can spend in channels; one-to-one DM usage from a member who has connected a Claude account bills to that member's own seat and follows the seat's usual limits.
482* **A switch for group DMs alone, or settings for one group DM.** You can't attach a bundle to one group DM, turn Claude off in one, or stop group DMs without also stopping one-to-one DMs or the workspace's channels. See [Group DMs](#group-dms).
480* **A switch for group DMs alone, or settings for one group DM.** You can't attach a bundle to one group DM, turn Claude off in one, or stop Claude from answering in group DMs without also stopping it in one-to-one DMs or the workspace's channels. See [Group DMs](#group-dms).
483481* **Per-channel responder allowlist.** The restriction toggle governs who can invoke Claude across the workspace; you can't narrow it to a list of people for one channel only.
484482* **An open-internet switch in Claude Tag settings.** A channel sandbox reaches only allowed hosts. To let Claude reach a public site or API, an Owner or a [Claude Tag admin](#delegate-claude-tag-administration) adds that hostname on a [bundle's Domains tab](/docs/claude-tag/admins/add-connections#allow-a-host-without-a-credential); for broad web access, an Owner pins an [environment](/docs/claude-tag/concepts/glossary#environment) whose network access level is Full access on the scope. [Allow-all egress](/docs/claude-tag/admins/add-connections#allow-all-hosts), a `*` entry on the Domains tab, admits any host on the ports it lists.
485483* **A web search toggle for channels.** No setting turns web search off for channel sessions; the web search capability setting in claude.ai admin settings governs claude.ai chat, not channels. Web search runs on Anthropic's servers rather than from the channel sandbox, so Domains entries and egress settings don't govern it, and a search opens no new path out of the sandbox; search requests travel to Anthropic the same way the session's model traffic already does. See [Web search vs. network requests](/docs/claude-tag/concepts/agent-identity#web-search-vs-network-requests).
claude-tag/concepts/data-lifecycle Changed · +5 / -5 lines
from line 43
4343
4444| Action | Claude-side data | Does Claude keep responding? |
4545| :- | :- | :- |
46| A Slack admin uninstalls the Claude app from a workspace | Deleted, the same as [disconnecting the workspace](#actions-in-claude), plus the app's installation credential for that workspace. Access bundles, and routines members set up in direct messages, stay | No. The app is removed from the workspace |
46| A Slack admin uninstalls the Claude app from a workspace | Deleted, the same as [disconnecting the workspace](#actions-in-claude), plus the app's installation credential for that workspace. Access bundles, and routines members set up in one-to-one direct messages, stay | No. The app is removed from the workspace |
4747| On Enterprise Grid, a Grid admin removes an org-wide installation of the app, from the whole grid or from one of its workspaces | Nothing is deleted. To delete the data, an Owner disconnects the grid, or a workspace that has its own pairing, in your Claude admin settings | No |
4848| A channel is deleted in Slack | Deleted: that channel's sessions and transcripts, including earlier sessions Claude had archived there, its channel memory, and its scope with the routines and artifacts that belong to it. Workspace notes Claude saved from a public channel aren't tied to the channel and stay until you delete them or disconnect the workspace, as does anything created under the workspace scope rather than the channel's own | Not applicable |
4949| A channel is archived in Slack | Nothing is deleted. Unarchiving the channel picks its memory, routines, and sessions back up | Not while the channel is archived |
from line 53
5353| Someone deletes a reply in a thread | Nothing is removed from the transcript, and Claude isn't notified | Yes |
5454| Someone deletes a thread's first message | Claude stops working in that thread. The session closes and is archived with its transcript, including the deleted message | No. Start a new thread to continue |
5555| Someone deletes a file they attached in a thread Claude worked in | The copy Claude took into the session stays with the session and its transcript | Yes |
56| A member's Slack account is deactivated | Nothing is deleted. Their account link, direct-message conversations and notes, and their messages in channel transcripts stay. Channel routines they created keep running, and routines they set up in direct messages keep running until they're removed from your Claude organization | Not to that member |
56| A member's Slack account is deactivated | Nothing is deleted. Their account link, direct-message conversations and notes, and their messages in channel transcripts stay. Channel routines they created keep running, and routines they set up in one-to-one direct messages keep running until they're removed from your Claude organization | Not to that member |
5757
5858### Actions in Claude
5959
6060| Action | Claude-side data | Does Claude keep responding? |
6161| :- | :- | :- |
62| An Owner [disconnects a workspace](/docs/claude-tag/admins/workspaces#revoke-a-pairing) | Deleted: the workspace's sessions and transcripts, including members' direct-message conversations there; its channel, workspace, and direct-message memory; the routines set up in its channels and the artifacts published from them; its scopes with their instructions and bundle bindings; and members' account links. The Slack app and its installation credential stay so a workspace admin can pair again, and Access bundles, routines members set up in direct messages, and what Claude posted in Slack stay too. Pairing the same workspace to the same organization again within a few minutes can cancel the deletion | Stops in channels immediately. One-to-one direct messages keep working on each member's own Claude account until the deletion removes that member's account link |
62| An Owner [disconnects a workspace](/docs/claude-tag/admins/workspaces#revoke-a-pairing) | Deleted: the workspace's sessions and transcripts, including members' direct-message conversations there; its channel, workspace, and direct-message memory; the routines set up in its channels and the artifacts published from them; its scopes with their instructions and bundle bindings; and members' account links. The Slack app and its installation credential stay so a workspace admin can pair again, and Access bundles, routines members set up in one-to-one direct messages, and what Claude posted in Slack stay too. Pairing the same workspace to the same organization again within a few minutes can cancel the deletion | Stops in channels immediately. One-to-one direct messages keep working on each member's own Claude account until the deletion removes that member's account link |
6363| An Owner disconnects an Enterprise Grid | The same as disconnecting a workspace, for every workspace in the grid that doesn't have its own workspace pairing, plus the app's installation credentials for those workspaces. Workspaces you paired individually stay connected and keep their data until you disconnect them | Stops in the affected workspaces |
6464| An Owner removes a channel's scope with **Remove this scope** in the **Claude Tag's access** section | Deleted: the channel's sessions and transcripts recorded up to that moment, including threads still in progress, its memory, its routines, and the artifacts published from it. The Slack channel itself is unchanged | Yes. Claude stays in the channel and, when tagged again, starts fresh under the access it inherits from the workspace. To stop it as well, run `/remove @Claude` or turn the scope's **Enable Claude Tag in this channel** switch off first |
6565| An Owner turns a scope's **Enable Claude Tag** switch off, turns off Claude in Slack for the organization, or turns off [direct messages](/docs/claude-tag/admins/restrict-access#allow-or-disable-direct-messages) | Nothing is deleted. Turning the setting back on resumes with the existing memory, routines, and sessions | No, in the affected scope |
from line 67
6767| An Owner deletes entries from a scope's memory files, or someone in the channel tells Claude to forget an entry | The entry is removed from what Claude reads and from the memory files view. Earlier versions of the scope's memory remain stored with the scope until the scope's data is deleted | Yes |
6868| An Owner deletes a channel's routine from the [**Scheduled work** tab](/docs/claude-tag/admins/audit#what-the-audit-view-lists), or someone asks Claude to delete a routine in the channel or direct message where it was set up | The routine and the sessions it ran are deleted. Pausing a routine there, or disabling it from the channel, keeps it on record | Yes |
6969| A member selects **Disconnect** in the Claude app's **Home** tab in Slack | Removes the link between their Slack and Claude accounts and revokes the tokens Claude Tag held for them. Their earlier direct-message conversations and notes, and channel work they started, aren't deleted; those go with the workspace | In channels, yes. One-to-one direct messages and personal connectors stop working for that member until they reconnect |
70| A member is removed from your Claude organization | Nothing is deleted. They lose access within minutes, and routines they set up in direct messages are turned off. Their account link, direct-message conversations, and notes stay until the workspace is disconnected | Not to that member |
70| A member is removed from your Claude organization | Nothing is deleted. They lose access within minutes, and routines they set up in one-to-one direct messages are turned off. Their account link, direct-message conversations, and notes stay until the workspace is disconnected | Not to that member |
7171| A member deletes their own Claude account | On Team and Enterprise plans, deleting an individual account doesn't remove the Claude Tag data your organization holds about that member, including their direct-message conversations and notes and their account link. A member who wants the link and its tokens removed can select **Disconnect** in Slack before deleting their account | Not to that member |
7272| Your Claude organization is deleted | All Claude Tag data for every paired workspace is deleted as part of the organization deletion. The Slack app isn't uninstalled by this, and its installation credential remains until the app is uninstalled, so uninstall it from each workspace in Slack as well | No |
7373| Your organization adopts Zero Data Retention or another restricted compliance configuration after pairing | Nothing already stored is deleted. Disconnect each workspace to delete its data | No. Claude stops responding in Slack and new pairings are refused; see [Restricted compliance settings block Claude Tag](/docs/claude-tag/admins/troubleshooting#restricted-compliance-settings-block-claude-tag) |
from line 76
7676
7777A direct-message conversation with Claude is stored the same way a channel thread is, as a session with a transcript, together with the notes Claude keeps for that conversation. Both are deleted with the workspace the member messaged Claude from, when that workspace is disconnected or the app is uninstalled from it, and when your Claude organization is deleted. They aren't deleted when the member selects **Disconnect** in Slack, when the member's Claude account is deleted on a Team or Enterprise plan, or when an Owner turns off direct messages.
7878
79Routines a member set up in a direct message belong to that member's Claude account. The member can ask Claude in the direct message to delete one. They are turned off when the member is removed from your Claude organization, and disconnecting the workspace doesn't delete them.
79Routines a member set up in a one-to-one direct message belong to that member's Claude account. The member can ask Claude in that direct message to delete one. They are turned off when the member is removed from your Claude organization, and disconnecting the workspace doesn't delete them.
8080
8181When a member first opens a direct message with Claude, the welcome Claude writes, which suggests channels based on the member's recent public-channel activity, runs as a short session that is stored like any other.
8282
claude-tag/users/group-dms Changed · +6 / -6 lines
from line 6
66
77<BetaNote />
88
9A group DM is a Slack direct message among several people. On the Team plan, and for some organizations on the Enterprise plan, Claude works in a group DM it has been added to, so a few people can share a task with Claude without creating a channel.
9A group DM is a Slack direct message among several people. Claude works in a group DM it has been added to, so a few people can share a task with Claude without creating a channel.
1010
11If Claude doesn't work in group DMs for your organization, it answers a top-level `@Claude` mention in a group DM with "Group DMs aren't supported yet. Try a channel or a 1:1 DM instead." That reply has [other causes](/docs/claude-tag/users/troubleshooting#group-dms-aren%E2%80%99t-supported-yet) too.
11If Claude answers your mention with "Group DMs aren't supported yet. Try a channel or a 1:1 DM instead.", see [the causes of that reply](/docs/claude-tag/users/troubleshooting#group-dms-aren%E2%80%99t-supported-yet).
1212
1313This page is for Slack members. It covers how to add Claude, what Claude can reach, when it replies, how to make it quieter, what differs from a channel, and what to do when Claude doesn't answer. If you administer Claude for your organization, see [the settings that apply to group DMs](/docs/claude-tag/admins/restrict-access#group-dms).
1414
from line 34
3434
3535## When Claude replies in a group DM
3636
37In a group DM, Claude reads the top-level messages, including the ones that don't mention it, unless someone [makes Claude quieter](#make-claude-quieter-in-a-group-dm) there.
37In a group DM, Claude reads the top-level messages, including the ones that don't mention it.
3838
3939* **You mention `@Claude` at the top level.** Claude replies in a thread under your message.
4040* **You reply in a thread that started with an `@Claude` mention.** Your reply reaches Claude without another mention.
from line 46
4646
4747### Quiet Claude in the whole group DM
4848
49Ask Claude to reply only when someone mentions it. The change applies to everyone in the group DM, and someone in the group DM has to confirm it. To confirm, a person needs a connected Claude account in your organization and can't be a Slack guest.
49Ask Claude to reply only when someone mentions it. The change applies to everyone in the group DM. To select **Confirm** on the card Claude posts, a person needs a connected Claude account in your organization and can't be a Slack guest.
5050
5151Claude can't make the change in these cases:
5252
from line 69
6969 </Step>
7070</Steps>
7171
72After the change, Claude stops reading top-level messages that don't mention it. It still answers a mention, and it still reads replies in a thread that started with an `@Claude` mention.
72After the change, Claude still answers a mention, and it still reads replies in a thread that started with an `@Claude` mention.
7373
7474To have Claude reply without a mention again, mention `@Claude` and ask.
7575
from line 99
9999
100100| What you see | Why Claude can't answer | What to do |
101101| :- | :- | :- |
102| "Group DMs aren't supported yet. Try a channel or a 1:1 DM instead." | Claude doesn't work in group DMs for your organization, or one of the other causes applies | See [Group DMs aren't supported yet](/docs/claude-tag/users/troubleshooting#group-dms-aren%E2%80%99t-supported-yet) |
102| "Group DMs aren't supported yet. Try a channel or a 1:1 DM instead." | Who is in the group DM, or how Slack shares it, keeps Claude from answering | See [Group DMs aren't supported yet](/docs/claude-tag/users/troubleshooting#group-dms-aren%E2%80%99t-supported-yet) |
103103| "Your Claude admin has disabled sending direct messages to Claude." | An admin turned off direct messages, which covers group DMs too | Ask in a channel, or ask your admin about turning direct messages on |
104104| "Claude doesn't respond in channels that include guests." | The group DM includes a Slack guest, and your admin's guest setting keeps Claude from replying | Start a group DM without the guest, or ask your admin about the guest setting |
105105| "Claude is disabled in this channel." | An admin turned Claude off for the workspace | Ask your admin about turning Claude on for the workspace |
claude-tag/users/troubleshooting Changed · +5 / -6 lines
from line 697
697697
698698Claude can't answer in this group DM. These are the usual causes:
699699
700* Claude doesn't work in group DMs for your organization. It works in [group DMs](/docs/claude-tag/users/group-dms) on the Team plan, and for some organizations on the Enterprise plan.
701700* The group DM includes someone from another company, through Slack Connect.
702* Your company uses Slack Enterprise Grid, and Slack shares the group DM across the Grid's workspaces.
701* Your company uses Slack Enterprise Grid, and the people in the group DM share no workspace.
703702
704703**How to resolve**
705704
706Ask Claude in a channel or a one-to-one DM instead. No admin setting makes Claude work in group DMs for an organization. If you're an admin, [Group DMs](/docs/claude-tag/admins/restrict-access#group-dms) covers how who is in a group DM, and how Slack shares it, can change whether Claude answers.
705Ask Claude in a channel or a one-to-one DM instead. If you're an admin, [Group DMs](/docs/claude-tag/admins/restrict-access#group-dms) covers how who is in a group DM, and how Slack shares it, can change whether Claude answers.
707706
708707### Agents can only be added at the start of direct messages
709708
claude-tag/admins/configure-github Changed · +1 / -1 lines
from line 147
147147
148148#### GitHub Enterprise Server in direct messages
149149
150In a [direct message](/docs/claude-tag/concepts/agent-identity#direct-message-channels), Claude reaches repositories on a registered host through the sender's own GitHub Enterprise account instead of the bundle's grants. Claude adds a repository to a DM session only when both of these are true:
150In a [one-to-one direct message](/docs/claude-tag/concepts/agent-identity#direct-message-channels), Claude reaches repositories on a registered host through the sender's own GitHub Enterprise account instead of the bundle's grants. Claude adds a repository to a DM session only when both of these are true:
151151
152152* The sender's GitHub Enterprise account has push access to the repository
153153* Your GitHub App's installation on the instance includes the repository
claude-tag/admins/customize Changed · +1 / -1 lines
from line 75
7575On the Team plan, Claude Tag doesn't apply the [`availableModels` allowlist](https://code.claude.com/docs/en/model-config#restrict-model-selection) from your Claude Code [server-managed settings](https://code.claude.com/docs/en/server-managed-settings), and on the Enterprise plan it applies the allowlist in only some organizations.
7676
7777* **Where the allowlist doesn't apply**: Claude offers your organization's full Claude Tag model list, both when someone asks it to switch and in the model selector for direct messages. It starts sessions on a scope's **Default model** without checking that model against the allowlist. The **Default model** picker in admin settings still lists only allowed models.
78* **Where the allowlist applies**: sessions in a channel run as the [agent identity](/docs/claude-tag/concepts/agent-identity) you provisioned and without your server-managed settings. When someone in a channel asks Claude to switch models, Claude may decline a model outside the allowlist, though that check doesn't always run. In direct messages from a member whose linked Claude account belongs to your organization, Claude runs on that member's own account, which receives your allowlist; see [Restrict model selection](https://code.claude.com/docs/en/model-config#restrict-model-selection) for what happens to a model the allowlist blocks.
78* **Where the allowlist applies**: sessions in a channel run as the [agent identity](/docs/claude-tag/concepts/agent-identity) you provisioned and without your server-managed settings. When someone in a channel asks Claude to switch models, Claude may decline a model outside the allowlist, though that check doesn't always run. In one-to-one direct messages from a member whose linked Claude account belongs to your organization, Claude runs on that member's own account, which receives your allowlist; see [Restrict model selection](https://code.claude.com/docs/en/model-config#restrict-model-selection) for what happens to a model the allowlist blocks.
7979
8080In either case, Claude Tag offers only the models it supports, so a model your allowlist includes can be absent in Slack.
8181
claude-tag/admins/federated-access/limits Changed · +1 / -1 lines
from line 10
1010
1111## Where federated connections work
1212
13Federated connections are available to Claude in Slack channels, where it acts under your organization's [agent identity](/docs/claude-tag/concepts/agent-identity). They aren't available in direct messages, which run on the individual's own claude.ai account, and they need an Anthropic-hosted environment; Claude can't use them in a [self-hosted environment](/docs/claude-tag/concepts/security-and-data).
13Federated connections are available to Claude in Slack channels, where it acts under your organization's [agent identity](/docs/claude-tag/concepts/agent-identity). They aren't available in one-to-one direct messages, which run on the individual's own claude.ai account, and they need an Anthropic-hosted environment; Claude can't use them in a [self-hosted environment](/docs/claude-tag/concepts/security-and-data).
1414
1515## Identity token
1616
claude-tag/admins/federated-access/overview Changed · +1 / -1 lines
from line 63
6363* Your cloud or gateway administrator configures the system on your side: the gateway operator, your AWS or Google Cloud IAM administrator, or your authorization server's operator. Each setup page lists the values they configure.
6464* An [Access bundle](/docs/claude-tag/admins/add-connections) is attached to the [scope](/docs/claude-tag/concepts/glossary#scope) of the channels where Claude should use the connection. To use a connection in several places, attach its bundle to each scope. A gateway can also be added to more than one bundle; an AWS role or authorization server is connected in one bundle only.
6565
66Federated connections work in Slack channels, where Claude acts under your organization's agent identity. They don't work in direct messages from members who have connected a Claude account, which run under [the individual's own account](/docs/claude-tag/concepts/agent-identity#direct-message-channels).
66Federated connections work in Slack channels, where Claude acts under your organization's agent identity. They don't work in one-to-one direct messages from members who have connected a Claude account, which run under [the individual's own account](/docs/claude-tag/concepts/agent-identity#direct-message-channels).
6767
6868## Related resources
6969
claude-tag/admins/set-spend-limit Changed · +1 / -1 lines
from line 85
8585* **Scheduled**: recurring scheduled work
8686* **Monitoring**: Claude reading the channels it belongs to, which isn't billed
8787
88Reading a channel Claude belongs to, whether or not anyone tags it, doesn't draw from the usage balance. When Claude starts a working session on its own, that session bills to the balance under Proactive. To stop Claude from starting work on its own in a channel, turn off the channel's [Respond automatically](/docs/claude-tag/users/when-claude-responds#turn-automatic-replies-on-or-off) setting. DMs from members who have connected a Claude account aren't included, because they bill to the sender's seat.
88Reading a channel Claude belongs to, whether or not anyone tags it, doesn't draw from the usage balance. When Claude starts a working session on its own, that session bills to the balance under Proactive. To stop Claude from starting work on its own in a channel, turn off the channel's [Respond automatically](/docs/claude-tag/users/when-claude-responds#turn-automatic-replies-on-or-off) setting. One-to-one DMs from members who have connected a Claude account aren't included, because they bill to the sender's seat.
8989
9090## Related resources
9191
claude-tag/admins/workspaces Changed · +1 / -1 lines
from line 132
132132 * Its scopes, with their instructions and bundle bindings
133133 * The links between members' Slack and Claude accounts
134134
135 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 direct message with Claude belong to that person's account and keep running.
135 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.
136136</Warning>
137137
138138Access 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.
claude-tag/concepts/personal-connectors Changed · +1 / -1 lines
from line 24
2424* **You ask in a channel.** When your task needs one of your own tools, Claude can use your connector for it. The channel also uses the connections an admin attached to it, and everyone who asks there gets the same access.
2525* **Someone else asks in a channel.** Your connectors serve only you. Their request doesn't control or use your connectors, even in a shared channel.
2626* **Claude starts work on its own.** [Routines](/docs/claude-tag/users/proactivity) and other work Claude starts on its own in a channel use the channel's connections, never your connectors.
27* **You ask in a [group DM](/docs/claude-tag/users/group-dms).** Claude asks you before it uses your connectors, and only your own requests use them.
27* **You ask in a [group DM](/docs/claude-tag/users/group-dms).** Claude uses your connectors after you allow it, and only your own requests use them.
2828* **You ask in a one-to-one direct message (DM).** Your connectors apply on their own, because a DM runs on [your own claude.ai account](/docs/claude-tag/concepts/agent-identity#direct-message-channels).
2929
3030To add or remove connectors on your account, open the **Customize > Connectors** page on claude.ai; see [connectors on claude.ai](/docs/connectors/getting-started) for setup.
claude-tag/users/getting-started Changed · +1 / -1 lines
from line 16
1616 * Example: `@Claude where are we on the launch checklist? Pull what's still open from this channel and #design-review.`
1717* **DM** for personal tasks. A one-to-one DM with Claude runs on your own claude.ai account with [your own connectors](/docs/connectors/getting-started). Every DM message reaches Claude without an @-mention. You can also DM Claude questions about getting started, like how to word a task or what to try first.
1818 * Example: `Pull my afternoon meetings from my calendar and draft a one-line prep note for each.`
19* **Group DM** for shared work among a few people, without creating a channel. Claude uses the access an admin set for the workspace and the organization, and the work bills to the organization. Claude works in group DMs on the Team plan, and for some organizations on the Enterprise plan. See [Use Claude Tag in a group DM](/docs/claude-tag/users/group-dms).
19* **Group DM** for shared work among a few people, without creating a channel. Claude uses the access an admin set for the workspace and the organization, and the work bills to the organization. See [Use Claude Tag in a group DM](/docs/claude-tag/users/group-dms).
2020 * Example: `@Claude draft a rollout checklist for the pricing page change.`
2121
2222See [team channels and personal DMs](/docs/claude-tag/concepts/how-it-works#team-channels-and-personal-dms) for the full comparison.