Home Docs Claude Documentation

One capture · claude-docs

One read of Claude Documentationclaude-docs-20260928T220706Z

157 pages moved out of 255 read.

Pages moved 157 significant first

Pages read 255 in this capture

Captured 28 Sep 2026 22:07 UTC

Corpus hash 9aad7bf66b91 corpus-hash

What this read moved

51-75 of 157, page 3 of 7

This capture is too large to show at once. Changes 51-75 of 157 are below, significant first; the rest are on the following screens.

claude-tag/admins/set-spend-limit Changed · +12 / -12 lines

from line 12

1212

1313Slack users can work with Claude in channels [without holding a Claude seat](/docs/claude-tag/admins/restrict-access#restrict-who-can-use-claude).

1414

15| Work | Bills to | Capped by |

16| :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :-------------------------------- | :---------------------------------------------------------------------------------------------------- |

17| Channel work | Your organization's usage balance | The spend limit, plus any [per-channel limits](/docs/claude-tag/admins/restrict-access#set-spend-limits) |

18| Reading a channel, [deciding whether to reply](/docs/claude-tag/users/when-claude-responds#what-claude-does-with-a-channel-message), and short replies from what Claude already knows | Nothing | Not counted toward any limit. A working session Claude starts from the channel is channel work, above |

19| A DM with Claude | The sender's own seat | The seat's usual limits, not the spend limit |

15| Work | Bills to | Capped by |

16| :- | :- | :- |

17| Channel work | Your organization's usage balance | The spend limit, plus any [per-channel limits](/docs/claude-tag/admins/restrict-access#set-spend-limits) |

19| A DM with Claude | The sender's own seat | The seat's usual limits, not the spend limit |

2020

2121## Whether this step is required depends on your plan

2222

23| Your plan | What you need to do here |

24| :------------------------ | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

25| **Team** | **Required, before anything runs.** A Team plan has no usage balance until it's funded, and Claude won't respond in channels until it is. A [launch usage credit](https://support.claude.com/en/articles/15575654-claude-tag-launch-promo-for-claude-team-and-enterprise) counts as a funded balance, so check for one before buying credits. Then set a spend limit. |

26| **Enterprise (invoiced)** | **Recommended.** Usage bills to your invoice with no upper bound until you set a spend limit. Set one to cap exposure during the pilot. |

23| Your plan | What you need to do here |

24| :- | :- |

26| **Enterprise (invoiced)** | **Recommended.** Usage bills to your invoice with no upper bound until you set a spend limit. Set one to cap exposure during the pilot. |

2727

2828## Set the spend limit

2929

from line 53

5353

5454When that happens, Claude tells the requester in the thread that it hit a rate limit and names a short wait, usually a few seconds. Re-send the message after the wait. Raising the spend limit doesn't clear a rate limit, and a rate-limited request doesn't spend anything.

5555

56| Claude says | Limit reached | What to do |

57| :--------------------------------------------------------------------- | :--------------- | :------------------------------------------------------------------------------------------------------------------- |

58| The spend limit is reached | Spend limit | Raise it on the usage page above |

56| Claude says | Limit reached | What to do |

57| :- | :- | :- |

58| The spend limit is reached | Spend limit | Raise it on the usage page above |

5959| It hit the session rate limit, or is rate limited delivering a message | Throughput limit | Wait the few seconds the reply names, then re-send. If your organization hits this often, contact your account team. |

6060

6161## Per-channel limits

claude-tag/admins/setup-overview Changed · +23 / -23 lines

from line 19

1919The console saves your progress, so you can leave and come back to where you stopped. When you've launched, [verify your setup](#verify-your-setup).

2020

2121<Accordion title="Before you start: check that you have what setup needs">

22 | Prerequisite | Why you need it | If you don't have it |

23 | :------------------------------------------------------------------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

24 | A **Team or Enterprise plan** on claude.ai | Claude Tag is available on Team and Enterprise plans, on Anthropic's first-party service. It isn't available on individual plans (Free, Pro, or Max), or for third-party deployments. | Start a Team or Enterprise plan at [claude.com/pricing](https://claude.com/pricing) |

25 | A Claude organization **without Zero Data Retention (ZDR) or customer-managed encryption (CMEK)** | Claude Tag stores channel memory and session transcripts, which ZDR doesn't permit. A CMEK policy doesn't allow Claude Tag either. | Claude Tag isn't available to organizations with a ZDR or CMEK policy |

26 | **Routines** enabled for your Claude organization | Until it is, Claude answers every mention and DM with a reply that it's unavailable and does no work. | An admin turns on [**Admin settings > Capabilities > Remote sessions > Routines**](https://claude.ai/admin-settings/capabilities) |

27 | **Owner** role in the Claude organization you're setting up | Pairing a workspace and creating Access bundles are Owner-only writes. Roles are per organization, so being an Owner elsewhere doesn't carry over. | Ask an Owner to run setup, or have one promote you at [`claude.ai/admin-settings/members`](https://claude.ai/admin-settings/members) |

28 | A **Slack workspace admin** | Running `@Claude connect` requires a Slack workspace admin; installing the app usually does too. | If that's someone else, [send them the install request](#if-you-re-not-the-slack-workspace-admin) early (app approval can take time), and plan to be online together when you pair; pairing codes expire 15 minutes after they're issued |

29 | **Usage credits** (Team plans) | Channel work draws from your organization's usage balance; on a Team plan nothing runs until credits are loaded. | Check whether your organization has a [launch usage credit](https://support.claude.com/en/articles/15575654-claude-tag-launch-promo-for-claude-team-and-enterprise) before buying; otherwise, buy credits at [`claude.ai/admin-settings/usage`](https://claude.ai/admin-settings/usage) |

30 | *(Optional)* The **Claude GitHub App** linked to your Claude organization | Linking GitHub first turns setup's GitHub step into repository selection instead of an app install. | [Link your GitHub organization](/docs/claude-tag/admins/configure-github#link-your-github-organization) first, or grant repository access after setup |

31 | *(Optional)* A **channel to test in** | You'll invite Claude to a channel to [verify your setup](#verify-your-setup). | Create a private Slack channel for the pilot, or pick any existing one |

22 | Prerequisite | Why you need it | If you don't have it |

23 | :- | :- | :- |

31 | *(Optional)* A **channel to test in** | You'll invite Claude to a channel to [verify your setup](#verify-your-setup). | Create a private Slack channel for the pilot, or pick any existing one |

3232

3333 If any of your services restrict traffic by IP, file the [network requirements](/docs/claude-tag/admins/network-requirements) request with your network team early; in many organizations, IP allowlist changes take days to approve.

3434

from line 245

245245

246246Every entry has the same sections: **Connectors**, **Repositories**, **Plugins**, **Custom instructions**, **Access bundles**, and, under **Advanced**, the **Default model**. An [Access bundle](/docs/claude-tag/concepts/glossary#access-bundle) is a named set of connections, repositories, plugins, and instructions that you can attach to more than one place. Setup created one on your workspace's entry, named after the workspace (for example, **Tag Test default**), holding the tools you connected.

247247

248| To do this | Go to | Learn more |

249| :---------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------- |

250| Change the model Claude replies with | The entry's **Advanced** section, **Default model**. Set it on **Default Slack** to change it everywhere, or on one channel. | [Choose the model for a scope](/docs/claude-tag/admins/customize#choose-the-model-for-a-scope) |

251| Give Claude standing instructions | The **Custom instructions** field on **Default Slack** for every channel, or on one channel's entry for that channel only. | [Customize](/docs/claude-tag/admins/customize) |

252| Connect another tool, or one you skipped | **Connectors** on the entry, or the bundle named after your workspace under **Access bundles**. | [Give Claude access](/docs/claude-tag/admins/add-connections) |

253| Let Claude reach a site or API that has no credential | The **Domains** list of the Access bundle, under **Access bundles**. | [Allow a host without a credential](/docs/claude-tag/admins/add-connections#allow-a-host-without-a-credential) |

254| Grant more repositories | **Repositories** on the entry. | [Configure GitHub access](/docs/claude-tag/admins/configure-github) |

255| Give one channel more than the default | Select the channel and add to it. | [Configure per-channel access](/docs/claude-tag/admins/attach-to-scope) |

256| Limit where Claude works or who can use it | | [Restrict where Claude operates](/docs/claude-tag/admins/restrict-access) |

257| Pair another workspace, or disconnect one | The Slack row's **⋮** menu under **Where Claude Tag works**. Disconnecting permanently deletes the workspace's Claude data. See [Data lifecycle and deletion](/docs/claude-tag/concepts/data-lifecycle). | [Manage workspaces](/docs/claude-tag/admins/workspaces) |

258| Change the spend limit | [`claude.ai/admin-settings/usage/claude-tag`](https://claude.ai/admin-settings/usage/claude-tag). | [Set a spend limit](/docs/claude-tag/admins/set-spend-limit) |

259| Turn Claude Tag off | The **Enable Claude Tag for your organization** toggle at the top of the admin page. | |

260| Bring in the first users | | [Getting started for users](/docs/claude-tag/users/getting-started) |

248| To do this | Go to | Learn more |

249| :- | :- | :- |

254| Grant more repositories | **Repositories** on the entry. | [Configure GitHub access](/docs/claude-tag/admins/configure-github) |

255| Give one channel more than the default | Select the channel and add to it. | [Configure per-channel access](/docs/claude-tag/admins/attach-to-scope) |

256| Limit where Claude works or who can use it | | [Restrict where Claude operates](/docs/claude-tag/admins/restrict-access) |

258| Change the spend limit | [`claude.ai/admin-settings/usage/claude-tag`](https://claude.ai/admin-settings/usage/claude-tag). | [Set a spend limit](/docs/claude-tag/admins/set-spend-limit) |

259| Turn Claude Tag off | The **Enable Claude Tag for your organization** toggle at the top of the admin page. | |

260| Bring in the first users | | [Getting started for users](/docs/claude-tag/users/getting-started) |

261261

262262## Common setup issues

263263

claude-tag/admins/skills-repo Changed · +11 / -11 lines

from line 38

3838

3939Once the repository is set up, Claude can propose changes and they reach channels automatically after you merge:

4040

41| Stage | What happens |

42| :------------------------ | :----------------------------------------------------------------------------------------------------------------------------------- |

43| Claude works in a channel | Using the skills currently attached to that scope |

41| Stage | What happens |

42| :- | :- |

43| Claude works in a channel | Using the skills currently attached to that scope |

4444| Claude proposes an update | Opens a pull request against the skills repository, under the Claude GitHub App identity, linked back to the thread that prompted it |

45| You review and merge | The PR is yours to approve, edit, or close, like any contributor's |

46| The marketplace syncs | On push to the default branch, the updated plugin syncs to your organization automatically |

47| New threads pick it up | The next thread in any covered channel uses the updated skill |

45| You review and merge | The PR is yours to approve, edit, or close, like any contributor's |

46| The marketplace syncs | On push to the default branch, the updated plugin syncs to your organization automatically |

47| New threads pick it up | The next thread in any covered channel uses the updated skill |

4848

4949Every skill change reaches channels only after a human approves the merge; Claude opens the PR, you merge it.

5050

from line 82

8282

8383## What belongs in the repository

8484

85| Put in the skills repo | Put in channel memory instead |

86| :------------------------------------------------------------ | :------------------------------------- |

87| How to call a specific API correctly | This channel's preferred output format |

88| A runbook that any team would reuse | A one-off decision this channel made |

89| Tool-specific gotchas (auth headers, pagination, rate limits) | Who owns what in this team |

85| Put in the skills repo | Put in channel memory instead |

86| :- | :- |

87| How to call a specific API correctly | This channel's preferred output format |

88| A runbook that any team would reuse | A one-off decision this channel made |

89| Tool-specific gotchas (auth headers, pagination, rate limits) | Who owns what in this team |

9090

9191Skills in the repository reach every channel under the scope.

9292

claude-tag/admins/troubleshooting Changed · +26 / -26 lines

from line 19

1919

2020What you expected to see while running [setup](/docs/claude-tag/admins/setup-overview), what appeared instead, and what to do.

2121

22| You expected | But got | Do this |

23| :----------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |

24| The setup page at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag) | A page titled **Set up Claude Tag** with **View setup guide** and **Go to chat** buttons | Your signed-in account can't run setup, and **View setup guide** leads back to this guide. On a personal account (Free, Pro, or Max), [start a Team or Enterprise plan](https://claude.com/pricing) first. In a Team or Enterprise organization, ask an Owner to run setup. When the page shows a workspace switcher, your account also belongs to another Team or Enterprise organization; switch to it and retry. |

25| A pairing code from `@Claude connect` | “Only Slack workspace admins (or Enterprise Grid org admins) can link this workspace to a Claude organization…” | The person who sent `@Claude connect` isn't a Slack workspace admin or Grid org admin. See [Only Slack workspace admins or Grid org admins can link this workspace](#only-slack-workspace-admins-or-grid-org-admins-can-link-this-workspace). |

26| A pairing code | “…installation is out of date” | A Slack admin approves the update or reinstalls the app, then sends `@Claude connect` again. See [This workspace's Claude app installation is out of date](#this-workspace%E2%80%99s-claude-app-installation-is-out-of-date). |

27| A pairing code | A message about guests, or about the channel being shared across workspaces | Send `@Claude connect` again in a channel with no guests that belongs to a single workspace. Match the exact message in [Guest and shared channels](#guest-and-shared-channels) for the fix that fits it. |

28| The console to accept your pairing code | "Claim code is invalid, expired, or already used" | Codes are single-use and last 15 minutes. Send `@Claude connect` again and paste the fresh code right away. See [Claim code is invalid, expired, or already used](#claim-code-invalid). |

29| The console to accept your pairing code | "Already connected to a different organization" | The workspace is paired to another Claude organization, often a trial org. See [Already connected to a different organization](#already-connected-to-a-different-organization). |

30| Your Claude account to connect after you select **Connect Claude account** | The browser page refuses the connection, and Claude DMs you "This workspace is connected to a different Claude organization" | The Claude account belongs to a different organization than the one the workspace is paired with. Connect an account from that organization; if the browser is signed in to another Claude account, sign out at claude.ai first. See [This workspace is connected to a different Claude organization](#this-workspace-is-connected-to-a-different-claude-organization). |

31| The spend limit picker on the **Launch Claude Tag** step | A **Buy usage credits** step | Your organization pays by card in US dollars and has no credits loaded. Load credits, or select **Skip** to continue without; nothing runs in channels until the balance is funded. Invoiced organizations and those billing in other currencies see the spend limit picker regardless of balance. |

32| A reply from Claude while you're still in setup | "Claude is disabled in this channel. Your admin can re-enable it here." | Claude Tag isn't turned on until you finish [Launch Claude Tag](/docs/claude-tag/admins/setup-overview#launch-claude-tag). Finish setup, then mention `@Claude` again. If the message persists after launch, see [Claude is disabled in this channel](#claude-is-disabled-in-this-channel). |

33| The **Connect GitHub** step to list your organization's repositories | "The Claude app is installed on \[username], a personal account. Claude Tag connects to a GitHub organization. Install it on your organization instead." | The Claude GitHub App is on a personal GitHub account. Have a GitHub organization owner [install it on the organization](/docs/claude-tag/admins/configure-github#link-your-github-organization) that owns your repositories. You can skip the step and [grant repositories](/docs/claude-tag/admins/configure-github#grant-repository-access) after setup. |

34| A connected tool to work in your test | “I can't reach…” | Claude isn't told about a connection added after the thread started. Ask it to use the service by name, or start a fresh thread. |

35| The **Where Claude Tag works** section with a **+ Connect** button | Only the legacy Claude in Slack toggles | Your organization isn't enabled for Claude Tag. Contact your account team. |

36| Claude to respond in Slack | "Claude Tag has been turned off for your Claude organization…" | The **Enable Claude Tag for your organization** toggle is off. An Owner turns it on at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag). See [the troubleshooting entry](#claude-tag-is-turned-off-for-your-organization). |

37| Claude to respond in Slack | "Claude Tag is unavailable because Routines aren't enabled for your organization…" | Routines isn't enabled for your Claude organization, which Claude Tag requires. An admin turns on [**Admin settings > Capabilities > Remote sessions > Routines**](https://claude.ai/admin-settings/capabilities). Anyone can then mention `@Claude` again. See [the troubleshooting entry](#claude-tag-is-unavailable-because-routines-are-not-enabled). |

38| Claude to respond in Slack | "Claude in Slack is not available for your organization" or "Claude isn't available for organizations with restricted compliance settings." | The paired Claude organization has a restricted compliance configuration, such as Zero Data Retention (ZDR), that Claude Tag can't run under. No setting lifts the restriction; contact your account team. See [the troubleshooting entry](#restricted-compliance-settings-block-claude-tag). |

39| The **Slack** tab to list your scopes | "Couldn't load Slack scopes. Reload the page to try again." | Reload the page. See [Couldn't load Slack scopes](#couldn%E2%80%99t-load-slack-scopes). |

40| A reply in your test channel | "Couldn't check this channel just now" | Mention `@Claude` again. See [Couldn't check this channel just now](#couldn%E2%80%99t-check-this-channel-just-now). |

41| A reply in your test channel | "Something went wrong starting a session" | Retry first. If it persists, see [the session-start entries](#something-went-wrong-starting-a-session). |

22| You expected | But got | Do this |

23| :- | :- | :- |

34| A connected tool to work in your test | “I can't reach…” | Claude isn't told about a connection added after the thread started. Ask it to use the service by name, or start a fresh thread. |

35| The **Where Claude Tag works** section with a **+ Connect** button | Only the legacy Claude in Slack toggles | Your organization isn't enabled for Claude Tag. Contact your account team. |

39| The **Slack** tab to list your scopes | "Couldn't load Slack scopes. Reload the page to try again." | Reload the page. See [Couldn't load Slack scopes](#couldn%E2%80%99t-load-slack-scopes). |

40| A reply in your test channel | "Couldn't check this channel just now" | Mention `@Claude` again. See [Couldn't check this channel just now](#couldn%E2%80%99t-check-this-channel-just-now). |

41| A reply in your test channel | "Something went wrong starting a session" | Retry first. If it persists, see [the session-start entries](#something-went-wrong-starting-a-session). |

4242

4343## Slack app permissions

4444

from line 739

739739

740740When Claude can name the cause, it posts one of these instead:

741741

742| Message | Cause |

743| ------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

744| "That message didn't get through to Claude." | Requests arrived faster than Claude accepts them at that moment; wait a few seconds, then mention Claude again |

745| A message naming a specific repository that isn't available or isn't configured | The repository isn't granted for this channel; see [GitHub doesn't work in this channel](#github-doesn%E2%80%99t-work-in-this-channel) |

742| Message | Cause |

743| - | - |

744| "That message didn't get through to Claude." | Requests arrived faster than Claude accepts them at that moment; wait a few seconds, then mention Claude again |

746746| "That environment or repo isn't configured for Claude Code. Check claude.ai/code and try again." | The scope's pinned environment isn't set up; see [Channel sessions use the wrong environment](#channel-sessions-use-the-wrong-environment-or-can%E2%80%99t-find-one) |

747| "Claude is having trouble starting sessions right now. Try again in a minute." | The service that runs sessions is briefly unavailable; retry |

748| "You don't have permission to start a session here." | A permission check refused to start the session; when Claude knows which check failed, the message names it |

747| "Claude is having trouble starting sessions right now. Try again in a minute." | The service that runs sessions is briefly unavailable; retry |

748| "You don't have permission to start a session here." | A permission check refused to start the session; when Claude knows which check failed, the message names it |

749749

750750**What it means**

751751

claude-tag/admins/workspaces Changed · +9 / -9 lines

from line 79

7979

8080The **Claude Tag version** setting is under the scope's **Advanced** section and is unavailable while the scope's switch is off. Choosing **Inherit** clears the scope's own setting entirely, so the scope also follows its parent for on or off.

8181

82| Label | Effect |

83| :---------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

84| **New** | Claude Tag. Access bundles, skills, and custom instructions apply |

85| **Legacy** | The earlier per-user Claude in Slack. Bundles and skills do not apply. Being deprecated; see [Migrate from the earlier app](/docs/claude-tag/admins/migrate-from-earlier) |

86| **Inherit** | Use the parent scope's value. Not shown at **Default Slack access** |

82| Label | Effect |

83| :- | :- |

84| **New** | Claude Tag. Access bundles, skills, and custom instructions apply |

85| **Legacy** | The earlier per-user Claude in Slack. Bundles and skills do not apply. Being deprecated; see [Migrate from the earlier app](/docs/claude-tag/admins/migrate-from-earlier) |

86| **Inherit** | Use the parent scope's value. Not shown at **Default Slack access** |

8787

8888Both versions answer through the same @Claude app, so turning a scope's **Enable Claude Tag** switch off silences the Legacy version there too. To opt out of Claude Tag while keeping the earlier behavior, leave the switch on and set the scope's **Claude Tag version** to **Legacy**.

8989

from line 113

113113

114114When a workspace or channel entry shows a notice that its settings aren't applied, nothing you set there is lost.

115115

116| Notice | What to do |

117| :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

118| "These settings aren't applied while Claude Tag is disabled. They're saved and will take effect once it's enabled." | Go to [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag) → **Claude Tag's access** → **Slack** → **Default Slack** → **Enable Claude Tag** and turn the switch on |

116| Notice | What to do |

117| :- | :- |

119119| "These settings aren't applied while Claude Tag is turned off for this workspace or channel; the org-wide Enable Claude Tag setting doesn't override that. They're saved and will take effect once it's turned back on." | The workspace, or the channel's workspace, was turned off on its own, and the switch doesn't override that. While you have the single switch, the admin page has no control for that workspace setting |

120| "These settings aren’t applied while Claude Tag setup is incomplete for this workspace or channel." | Select the **Resume** *workspace* **setup** button beside the notice and finish that workspace's setup. On a channel's entry, the button's label names the channel's workspace |

121121

122122## Revoke a pairing

123123

claude-tag/concepts/agent-identity Changed · +17 / -17 lines

from line 56

5656

5757For each outbound request from the sandbox, Agent Proxy checks the destination against three allow layers. A request goes through if any one of them allows it; a host that none of them allows is blocked.

5858

59| When the destination | Result |

60| :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------- |

61| Matches a connection's rule, its [allowed websites](/docs/claude-tag/admins/add-connections#set-allowed-websites) | The proxy attaches that connection's credential and forwards the request. The credential stays at the proxy; the model and sandbox are not given it. |

62| Is on the [bundle](/docs/claude-tag/concepts/glossary#access-bundle)'s [Domains list](/docs/claude-tag/admins/add-connections#allow-a-host-without-a-credential) but matches no connection | The proxy forwards the request without a credential. |

63| Is allowed by the network access setting of the [environment](/docs/claude-tag/concepts/glossary#environment) the [scope](/docs/claude-tag/concepts/glossary#scope)'s sessions run on | The proxy forwards the request without a credential. |

64| Matches none of these | The proxy blocks the request. |

59| When the destination | Result |

60| :- | :- |

64| Matches none of these | The proxy blocks the request. |

6565

6666A new environment's network access level defaults to Trusted access, so a fresh setup can reach a documented set of package registries and developer hosts before an admin has configured anything. The [cloud environments documentation](https://code.claude.com/docs/en/cloud-environments#default-allowed-domains) lists the covered hosts. To narrow that default, pin an environment with a stricter level, such as No access.

6767

from line 114

114114

115115The table lines up the two paths on the four dimensions that differ.

116116

117| | In a channel | In a DM |

118| :---------- | :--------------------------------------------- | :------------------------------------------------------------------- |

119| Acts as | Its own service accounts | You |

120| Access | The channel's Access bundles | Your personal connectors |

117| | In a channel | In a DM |

118| :- | :- | :- |

119| Acts as | Its own service accounts | You |

120| Access | The channel's Access bundles | Your personal connectors |

121121| Attribution | The agent's accounts, in each tool's audit log | Your name, except pull requests, which the Claude GitHub App authors |

122| Billing | The organization | Your seat |

123123

124124Three of those differences are worth spelling out.

125125

from line 135

135135

136136A DM with Claude Tag runs under your own account, which is also how [Claude Code in Slack](https://code.claude.com/docs/en/slack) works, routing a coding @-mention to a Claude Code session on the web under the requester's own account. The two can look identical. The table shows how to tell them apart.

137137

138| | Claude Tag in a channel | Claude Code in Slack |

139| :------------- | :----------------------------------------------------- | :------------------------------------------------------------------------------ |

140| **Runs under** | The agent identity an admin provisioned | Your own Claude account, linked in the Claude app |

141| **GitHub** | The Claude GitHub App; pull requests belong to the app | Your GitHub connection on claude.ai/code; pull requests open under your account |

142| **Access** | The Access bundles an admin attached to the channel | Your personal connectors |

143| **Billing** | The organization | Your seat |

138| | Claude Tag in a channel | Claude Code in Slack |

139| :- | :- | :- |

140| **Runs under** | The agent identity an admin provisioned | Your own Claude account, linked in the Claude app |

141| **GitHub** | The Claude GitHub App; pull requests belong to the app | Your GitHub connection on claude.ai/code; pull requests open under your account |

142| **Access** | The Access bundles an admin attached to the channel | Your personal connectors |

143| **Billing** | The organization | Your seat |

144144

145145If `@Claude` in your workspace opens pull requests as you, you're seeing Claude Code in Slack, not a Claude Tag session.

146146

claude-tag/concepts/data-lifecycle Changed · +37 / -37 lines

from line 12

1212

1313There are two copies of the work Claude does in Slack. The messages, canvases, files, bookmarks, and pins in Slack stay in Slack under your workspace's own retention settings. Anthropic doesn't remove them when Claude-side data is deleted, and can't once the app is uninstalled, so delete those in Slack. On Anthropic's side, Claude Tag stores the following for each paired workspace.

1414

15| What | What it contains |

16| :-------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |

17| Session transcripts | The record of one thread's, channel's, or direct message's work. A transcript holds the messages Claude was shown in the conversation and who sent them, files attached there, earlier versions of messages that were later edited, what Claude retrieved while working (Slack search results, messages it read in channels it's in, and data from connected tools), and everything Claude said and did |

18| Memory | The notes Claude saves for each channel, the workspace notes it saves from public channels, and separate notes for each direct-message conversation. See [What Claude Tag remembers](/docs/claude-tag/users/memory) |

19| Routines | The scheduled and run-once tasks set up in channels or in direct messages, with their instructions and run history |

20| Scopes and their settings | Each workspace and channel [scope](/docs/claude-tag/concepts/glossary#scope), with its custom instructions, version setting, and Access bundle bindings |

21| Access bundles | The connections and credentials an Owner provisions. Bundles belong to your organization, not to a workspace |

22| Account links | The link between each member's Slack account and their Claude account, and the tokens that link uses |

23| Published artifacts | Pages a session published to claude.ai. See [Artifact visibility](/docs/claude-tag/concepts/security-and-data#artifact-visibility) |

24| The app's installation credential | The token the Claude app uses to read and post in your Slack workspace |

15| What | What it contains |

16| :- | :- |

19| Routines | The scheduled and run-once tasks set up in channels or in direct messages, with their instructions and run history |

20| Scopes and their settings | Each workspace and channel [scope](/docs/claude-tag/concepts/glossary#scope), with its custom instructions, version setting, and Access bundle bindings |

21| Access bundles | The connections and credentials an Owner provisions. Bundles belong to your organization, not to a workspace |

22| Account links | The link between each member's Slack account and their Claude account, and the tokens that link uses |

23| Published artifacts | Pages a session published to claude.ai. See [Artifact visibility](/docs/claude-tag/concepts/security-and-data#artifact-visibility) |

24| The app's installation credential | The token the Claude app uses to read and post in your Slack workspace |

2525

2626Deleting or editing a message or file in Slack doesn't remove it from a transcript that already includes it. Messages from other people in the conversation, including guests, become part of the transcript the same way and are held as your organization's data.

2727

from line 41

4141

4242### Actions in Slack

4343

44| Action | Claude-side data | Does Claude keep responding? |

45| :------------------------------------------------------------------------------------------------------------------------------ | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :---------------------------------------- |

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 |

47| 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 |

48| 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 |

49| 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 |

50| A public channel is made private | Nothing is deleted. Claude archives the channel's earlier sessions. The channel's notes stay with the channel, and workspace notes Claude saved from it while it was public stay shared; see [Channel and workspace memory](/docs/claude-tag/users/memory#channel-and-workspace-memory) | Yes |

51| Someone removes Claude from a channel with `/remove @Claude` | Nothing is deleted. The channel's memory, routines, and past sessions stay on record, and re-adding Claude picks them back up. The channel's routines keep firing while Claude is out of the channel but can't post there | No |

52| Someone edits a message Claude read | Claude receives the edit as a note, and the transcript keeps both the earlier and the edited text | Yes |

53| Someone deletes a reply in a thread | Nothing is removed from the transcript, and Claude isn't notified | Yes |

54| 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 |

55| 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 |

44| Action | Claude-side data | Does Claude keep responding? |

45| :- | :- | :- |

49| 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 |

52| Someone edits a message Claude read | Claude receives the edit as a note, and the transcript keeps both the earlier and the edited text | Yes |

53| Someone deletes a reply in a thread | Nothing is removed from the transcript, and Claude isn't notified | Yes |

55| 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 |

5757

5858### Actions in Claude

5959

60| Action | Claude-side data | Does Claude keep responding? |

61| :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |

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. Direct messages keep working on each member's own Claude account until the deletion removes that member's account link |

63| 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 |

64| 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 |

65| 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 |

66| An Owner detaches a bundle from a scope, or deletes an Access bundle | Detaching removes the binding, and deleting a bundle removes its credentials everywhere it was attached. Memory, routines, and transcripts are unaffected | Yes, without that access |

67| 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 |

68| An Owner deletes a routine from the [**Scheduled work** tab](/docs/claude-tag/admins/audit#what-the-audit-view-lists), or someone asks Claude to delete it 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 |

69| 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. 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 |

71| 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 |

72| 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 |

73| 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) |

60| Action | Claude-side data | Does Claude keep responding? |

61| :- | :- | :- |

7474

7575## Direct messages

7676

claude-tag/concepts/for-claude-code-users Changed · +15 / -15 lines

from line 16

1616

1717A session begins with a fresh sandbox and no repository checked out. Your repository's Claude Code configuration takes effect only after Claude clones the repository, which happens when your message names a repository that an admin has [granted to the channel](/docs/claude-tag/admins/configure-github#grant-repository-access).

1818

19| Step | What applies |

20| :-------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |

21| You tag `@Claude` with a task | Your message is the task, and Claude starts work in a sandbox with no repository |

22| Your message names a granted repository | Claude clones it into the sandbox |

23| The clone completes | `CLAUDE.md`, `.claude/CLAUDE.md`, `.claude/rules/*.md`, and the skills in `.claude/skills/` [load into the session](/docs/claude-tag/admins/configure-github#what-loads-from-a-repository) |

19| Step | What applies |

20| :- | :- |

21| You tag `@Claude` with a task | Your message is the task, and Claude starts work in a sandbox with no repository |

22| Your message names a granted repository | Claude clones it into the sandbox |

2424

2525[Hooks](https://code.claude.com/docs/en/hooks) in the repository's `.claude/settings.json` don't run in the session.

2626

from line 34

3434

3535The table shows what takes the place of each setting from your machine. Where a counterpart exists, an admin sets it for the whole channel.

3636

37| Claude Code setting on your machine | In Claude Tag |

38| :--------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

39| `/model` | An admin sets the [default model per channel](/docs/claude-tag/admins/customize#choose-the-model-for-a-scope), and you can [switch models in a thread](/docs/claude-tag/users/models) |

40| Effort level | Not configurable. Sessions run at the model's default effort. |

41| MCP servers in `.mcp.json` | Not loaded, even when `.mcp.json` is checked into the repository. A session reaches external services only through the [connections an admin set for the channel](/docs/claude-tag/admins/add-connections), and each connection holds that service's credentials. |

42| Secrets and API keys in your environment | An admin provisions them as channel connections. The raw key never enters the sandbox. It is [added to requests at the network layer](/docs/claude-tag/concepts/agent-identity#agent-proxy). |

43| Environment variables | An admin sets them on the [environment the channel's sessions run on](/docs/claude-tag/admins/customize#configure-the-environment-for-a-scope), and every session in the channel reads them. There is no per-person environment to customize. The values are readable in every session on the environment, so ask an admin to add secrets as connections instead. |

44| A personal `settings.json` | Not loaded. |

45| A setup script for your workspace | An admin sets a setup script on the [environment the channel's sessions run on](/docs/claude-tag/admins/customize#configure-the-environment-for-a-scope), and what it installs is in place when each session in the channel starts. For setup that belongs to one repository, use `CLAUDE.md` [install steps](/docs/claude-tag/admins/configure-github#install-project-dependencies) instead. |

46| Permission prompts | Sessions run in auto mode, where Claude's permission checker reviews each action and can stop it. An admin pre-approves routine actions with [auto mode allow rules](/docs/claude-tag/admins/customize#auto-mode-allow-rules) instead of you approving in the moment. |

37| Claude Code setting on your machine | In Claude Tag |

38| :- | :- |

39| `/model` | An admin sets the [default model per channel](/docs/claude-tag/admins/customize#choose-the-model-for-a-scope), and you can [switch models in a thread](/docs/claude-tag/users/models) |

40| Effort level | Not configurable. Sessions run at the model's default effort. |

44| A personal `settings.json` | Not loaded. |

4747

4848To change what a session can reach for everyone, ask an admin to [add a connection](/docs/claude-tag/admins/add-connections). The change applies to every session in the channel.

4949

claude-tag/concepts/glossary Changed · +6 / -6 lines

from line 30

3030

3131Claude Tag is the second generation of the Claude app in Slack:

3232

33| | Legacy (the earlier Claude in Slack) | New (Claude Tag) |

34| :------------- | :------------------------------------------ | :------------------------------------------------------------------- |

35| Identity | Each user links their own claude.ai account | One agent identity with org-level service credentials |

36| Sessions | Spawned per request | One persistent session per thread, shared |

37| Memory | None | Per-channel memory, plus workspace notes shared from public channels |

38| Proactive work | None | Routines and channel watching |

33| | Legacy (the earlier Claude in Slack) | New (Claude Tag) |

34| :- | :- | :- |

35| Identity | Each user links their own claude.ai account | One agent identity with org-level service credentials |

36| Sessions | Spawned per request | One persistent session per thread, shared |

37| Memory | None | Per-channel memory, plus workspace notes shared from public channels |

38| Proactive work | None | Routines and channel watching |

3939

4040Your admin chooses which generation answers `@Claude` in a given channel, so two channels in the same workspace can work differently. See [Migrate from the earlier Claude in Slack](/docs/claude-tag/admins/workspaces#turn-claude-tag-on-or-off-and-set-the-version-for-a-scope).

4141

claude-tag/concepts/how-it-works Changed · +31 / -31 lines

from line 114

114114

115115Where you message Claude determines whose tools and accounts it uses. In a channel, it acts with the connections an organization admin set for that channel, and the work is attributed to its own accounts. In a DM, the same engine runs with your own claude.ai connectors, and the work is attributed to you, except pull requests, which the Claude GitHub App authors from DMs as well.

116116

118| :---------- | :----------------------------------------- | :----------------------- | :--------------------------------- |

120| A DM | Your own claude.ai connectors | You | Personal tasks using your own data |

118| :- | :- | :- | :- |

120| A DM | Your own claude.ai connectors | You | Personal tasks using your own data |

121121

122122The Access column is about external systems. A channel session reaches what the channel was granted, and a DM session reaches what your own account is connected to.

123123

from line 127

127127

128128Anthropic offers several ways to work with Claude on real tasks; they reach the same kinds of systems but through different mechanisms.

129129

131| :---------------- | :---------------------------------------------------------------- | :------------------------------------ | :------------------------------------------- |

131| :- | :- | :- | :- |

136136

137137The short version: **team work → Claude Tag; personal work → Cowork or Claude Code.** Claude Tag's connections authenticate the agent itself with service accounts, not any person. Personal connectors apply in a Claude Tag DM, which runs on your own claude.ai account, the same way Cowork does.

138138

from line 176

176176

177177Claude posts each session's result in the thread you asked in, choosing the form that fits the work.

178178

179| Form | What it is | When you see it |

180| :------------------ | :------------------------------------------------------ | :--------------------------------- |

181| A reply | An answer, list, or summary as a Slack message | Questions and short results |

182| A file or chart | Attached to the thread the way anyone shares a file | Data, images, generated documents |

183| A page kept current | Any of the above, edited in place over time | Digests, indexes, standing reports |

184| A hosted page | A web page published on claude.ai, linked in the thread | Dashboards, prototypes, reports |

179| Form | What it is | When you see it |

180| :- | :- | :- |

181| A reply | An answer, list, or summary as a Slack message | Questions and short results |

182| A file or chart | Attached to the thread the way anyone shares a file | Data, images, generated documents |

183| A page kept current | Any of the above, edited in place over time | Digests, indexes, standing reports |

184| A hosted page | A web page published on claude.ai, linked in the thread | Dashboards, prototypes, reports |

185185

186186A hosted page stays available after the session ends, and Claude updates it when you ask in the thread. Anyone with access to the channel can open it. [Artifact visibility](/docs/claude-tag/concepts/security-and-data#artifact-visibility) covers the access model. These are the same artifacts [Claude Code publishes](https://code.claude.com/docs/en/artifacts), with channel-based access in place of owner-controlled sharing.

187187

from line 213

213213

214214Where you ask decides what Claude can do in the other channel:

215215

216| Where you ask | Read the other channel | Post, reply, or react there |

217| :---------------- | :------------------------------------------------- | :------------------------------------------------------------------- |

218| A public channel | Yes, unless the channel you ask in includes guests | Yes |

219| A private channel | Yes, unless the channel you ask in includes guests | No |

220| A DM with Claude | Yes | New top-level posts only, each after you select **Approve and post** |

216| Where you ask | Read the other channel | Post, reply, or react there |

217| :- | :- | :- |

218| A public channel | Yes, unless the channel you ask in includes guests | Yes |

219| A private channel | Yes, unless the channel you ask in includes guests | No |

220| A DM with Claude | Yes | New top-level posts only, each after you select **Approve and post** |

221221

222222* **Attribution line**: every message Claude posts outside the conversation you asked from carries a line under it that names where it came from. When you ask in a thread, the line links back to that thread and names whoever last addressed Claude there, as in "Sent by Claude in #team-eng on behalf of @jordan". When you ask in a DM, the line names the person who approved the post, as in "Sent by Claude, approved by @jordan".

223223* **Replies**: replies under a message Claude posted in another channel don't reach the session you asked in. To follow up on the original task, reply in the thread where you asked.

from line 243

243243

244244A thread is durable, but the sandbox behind it is not. Durable means the thread stays in Slack, and everything Claude read and said in it is kept in the session's transcript on Anthropic's side, so the session can pick up where it left off whenever someone replies. Deleting messages or the thread in Slack doesn't remove them from that transcript. The sandbox is the computer where Claude runs commands and keeps working files for a task. A few minutes after a session finishes its turn, its sandbox is released, and the same session resumes in a fresh one when the next message arrives. A thread's session keeps resuming this way for as long as people use the thread. Claude replaces it with a new session in two cases.

245245

246| When | What Claude does |

247| :-------------------------------------------------------------------------------------------------------------------------- | :----------------------------------------------------------------------------- |

248| Someone sends [`@Claude !restart`](/docs/claude-tag/users/commands#restart-a-stuck-or-wrong-context-session) | Archives the session right away and starts a fresh one that rereads the thread |

249| The session [gets stuck and fails](/docs/claude-tag/users/troubleshooting#claude-reacted-or-started-thinking-then-never-replied) | Starts the replacement when the next message arrives in the thread |

246| When | What Claude does |

247| :- | :- |

248| Someone sends [`@Claude !restart`](/docs/claude-tag/users/commands#restart-a-stuck-or-wrong-context-session) | Archives the session right away and starts a fresh one that rereads the thread |

250250

251251<img className="block dark:hidden" src="https://mintcdn.com/claude-ai/5JFKyLlO7sHMMf5J/images/claude-tag/diagrams/session-lifecycle.svg?fit=max&auto=format&n=5JFKyLlO7sHMMf5J&q=85&s=9a56231787b03f179e8d552d887778fc" alt="Timeline with two lanes. The Slack thread lane is one continuous bar that persists from the moment a task starts. The sandbox lane below it is segmented, built when the task starts, released while the thread goes quiet, and rebuilt fresh when someone replies." width="1000" height="270" data-path="images/claude-tag/diagrams/session-lifecycle.svg" />

252252

253253<img className="hidden dark:block" src="https://mintcdn.com/claude-ai/5JFKyLlO7sHMMf5J/images/claude-tag/diagrams/session-lifecycle-dark.svg?fit=max&auto=format&n=5JFKyLlO7sHMMf5J&q=85&s=0693a90b98baa729dcacfd35261f6494" alt="Timeline with two lanes. The Slack thread lane is one continuous bar that persists from the moment a task starts. The sandbox lane below it is segmented, built when the task starts, released while the thread goes quiet, and rebuilt fresh when someone replies." width="1000" height="270" data-path="images/claude-tag/diagrams/session-lifecycle-dark.svg" />

254254

255| | Survives idle periods |

256| :------------------------------------- | :---------------------------------- |

257| The conversation and its context | Yes |

258| Channel memory | Yes |

259| Work pushed, posted, or opened as a PR | Yes, in the external system |

260| Files that exist only in the sandbox | No. Claude recreates them if asked. |

255| | Survives idle periods |

256| :- | :- |

257| The conversation and its context | Yes |

258| Channel memory | Yes |

259| Work pushed, posted, or opened as a PR | Yes, in the external system |

260| Files that exist only in the sandbox | No. Claude recreates them if asked. |

261261

262262For long tasks, ask it to push branches and post drafts as it goes, so deliverables are saved somewhere durable while the work is still running. See [Good habits](/docs/claude-tag/users/good-habits#give-every-task-a-definition-of-done).

263263

claude-tag/concepts/security-and-data Changed · +5 / -5 lines

from line 20

2020

2121<img className="hidden dark:block" src="https://mintcdn.com/claude-ai/oY6LusJt4c576Dc3/images/claude-tag/diagrams/request-path-dark.svg?fit=max&auto=format&n=oY6LusJt4c576Dc3&q=85&s=a728805c81b642004e1e15da96967e4c" alt="Diagram showing the request path across three zones, labeled your Slack workspace, Anthropic's infrastructure, and your systems. A task mentioned in the Slack workspace runs in a session sandbox in the middle zone, one sandbox per thread, holding no credentials. Outbound requests pass to Agent Proxy, which injects the credential drawn from the credential store; a request that no rule, domain entry, or environment network access setting allows is blocked. Credentialed requests reach your systems, like GitHub, a data warehouse, monitoring, or any HTTP API. A dashed return path shows results posting back in the thread, as Claude." width="1000" height="440" data-path="images/claude-tag/diagrams/request-path-dark.svg" />

2222

23| Checkpoint | The guarantee |

24| :----------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

25| The sandbox | Holds no credentials |

26| Agent Proxy | Injects credentials from the credential store at request time, and blocks a request that no [connection](/docs/claude-tag/admins/add-connections#set-allowed-websites), [**Domains** entry](/docs/claude-tag/admins/add-connections#allow-a-host-without-a-credential), or [environment network access level](/docs/claude-tag/admins/add-connections#broad-web-access-through-the-environment) allows |

27| Your systems | See the agent's own accounts, so its actions there are attributable |

23| Checkpoint | The guarantee |

24| :- | :- |

25| The sandbox | Holds no credentials |

27| Your systems | See the agent's own accounts, so its actions there are attributable |

2828

2929### Compute and the sandbox

3030

claude-tag/concepts/settings-map Changed · +7 / -7 lines

from line 8

99Claude Tag's settings live on claude.ai, split across a few pages that each own a different kind of setting. Which page you need depends on what you're changing. The table maps each surface to what it controls.

1010

11| Surface | Who changes it | What it controls |

12| :--------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

13| [Claude Tag admin page](https://claude.ai/admin-settings/claude-tag) | An Owner in your Claude organization | Access, behavior, and restrictions for channels, mostly per [scope](/docs/claude-tag/concepts/glossary#scope) |

14| [Usage page](https://claude.ai/admin-settings/usage/claude-tag) | An admin | Spend limits and each channel's spend against them |

15| [Analytics page](https://claude.ai/analytics/claude-tag) | Anyone who can view the Analytics dashboard | Spend trends, projections, and per-channel reports; read-only |

16| The **Configure** link in the footer of any Claude reply in a channel | Channel members (unless an admin restricts editing) and [channel managers](/docs/claude-tag/admins/restrict-access#delegate-channel-setup-to-channel-managers) for their assigned channels | One channel's instructions and whether Claude replies there without an @-mention. Channel managers also set the channel's default model, repositories, connections, and plugins |

17| [Customize > Connectors](https://claude.ai/customize/connectors) on your own claude.ai account | You | Which of your personal tools apply in [DMs](/docs/claude-tag/concepts/agent-identity#direct-message-channels) and for [your own tasks in a channel](/docs/claude-tag/concepts/personal-connectors) |

11| Surface | Who changes it | What it controls |

12| :- | :- | :- |

14| [Usage page](https://claude.ai/admin-settings/usage/claude-tag) | An admin | Spend limits and each channel's spend against them |

15| [Analytics page](https://claude.ai/analytics/claude-tag) | Anyone who can view the Analytics dashboard | Spend trends, projections, and per-channel reports; read-only |

1818

1919Channel memory and routines aren't in the table because you change them by talking to Claude in the channel; see [what anyone can change from the channel](/docs/claude-tag/admins/customize#change-behavior-from-the-channel). Owners can review both, as each scope's memory files and scheduled work, from [the Audit page](/docs/claude-tag/admins/audit), labeled **Activity** in the console.

2020

claude-tag/users/getting-started Changed · +14 / -14 lines

from line 51

5151

5252The footer under each reply names the model that handled it. You can [choose a different model](/docs/claude-tag/users/models) yourself, and admins [set the default model for each channel](/docs/claude-tag/admins/customize#choose-the-model-for-a-scope). In a channel, the footer also has a **Configure** link; open it to [tailor how Claude works in this channel](/docs/claude-tag/users/good-habits#configure-claude-for-a-channel). Replies in DMs and in org-shared channels have no Configure link.

5353

54| If you see | It means | Do this |

55| :------------------------------------------------------------------------------------ | :--------------------------------------------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------- |

56| Typing `@Claude` doesn't show **Claude** with an **APP** badge in the suggestion list | The Claude app isn't installed in your workspace | Ask your Slack admin to install the Claude app, and send them [the installation guide](/docs/claude-tag/admins/setup-overview#pair-your-slack-workspace) |

57| The mention sends but Claude doesn't reply | Setup isn't finished for this channel | Ask your Claude organization admin to enable Claude Tag for this channel, and send them [the setup guide](/docs/claude-tag/admins/setup-overview) with the channel name |

58| Claude replies "I couldn't find a Claude Code environment for your account" | Claude couldn't resolve an environment for this DM; DMs run on your account rather than the organization's | Mention Claude again. If it keeps happening, see [I get an environment error in a DM](/docs/claude-tag/users/troubleshooting#i-get-an-environment-error-in-a-dm) |

54| If you see | It means | Do this |

55| :- | :- | :- |

5959

6060## Hand Claude a task

6161

from line 79

7979

8080After you've handed Claude a task, the first question is what it has to work with. The short version: it reads the thread you tagged it in, it can search your workspace's public channels, and anything beyond Slack depends on what your admin connected.

8181

82| What you give Claude | Can Claude read it? |

83| :---------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

84| Messages in this thread | Yes. Mentioning it mid-thread also gives it the thread's earlier messages |

85| A file you attach (image, screenshot, PDF, or another type) | Yes, up to a size limit that depends on the file type. See [Files you attach](#files-you-attach) |

86| Other public channels in your workspace | By searching only, the same way a person searches Slack; Claude can find a message by keyword but can't read a channel's full history unless it's been added there |

87| Private channels and DMs | Only from inside them. Adding Claude to a private channel lets it work there, but the channel stays unreadable from any other channel or DM. |

88| A link you paste, like a Google Doc or a webpage | If your admin allowed that site for this channel, or, for a file behind your own login, if you've [allowed Claude to use your connectors](/docs/claude-tag/concepts/personal-connectors). If neither applies, Claude tells you it can't reach it. |

89| A Slack canvas | No |

90| A message you edited after sending | Yes. Each edit sends Claude a note showing the text before and after the edit. An edit never starts a new task on its own, so to be sure a correction is picked up, say it in a new reply; see [Reply in the thread to steer](/docs/claude-tag/concepts/how-it-works#reply-in-the-thread-to-steer) |

82| What you give Claude | Can Claude read it? |

83| :- | :- |

84| Messages in this thread | Yes. Mentioning it mid-thread also gives it the thread's earlier messages |

85| A file you attach (image, screenshot, PDF, or another type) | Yes, up to a size limit that depends on the file type. See [Files you attach](#files-you-attach) |

87| Private channels and DMs | Only from inside them. Adding Claude to a private channel lets it work there, but the channel stays unreadable from any other channel or DM. |

89| A Slack canvas | No |

9191

9292The fastest way to find out for your channel is to ask: `@Claude can you read the doc I just linked?` gets you a yes or a "that site isn't allowed here."

9393

claude-tag/users/good-habits Changed · +20 / -20 lines

from line 62

6262

6363Without a stated end condition, Claude can't declare the thread finished and you can't stop checking it. The end condition you write determines who can close the thread, and the table matches each kind of condition to who closes it.

6464

65| End condition | Who closes it | Example |

66| :----------------------------- | :----------------- | :---------------------------------------------------- |

67| An objective check passes | Claude, on its own | "Done when CI is green" |

68| You approve a prepared result | You, one click | "Draft the status memo and post it here for approval" |

69| You choose between options | You, one word | "Research approaches A and B and recommend one" |

70| No verifiable condition exists | No one | Reframe it as a question instead of a task |

65| End condition | Who closes it | Example |

66| :- | :- | :- |

67| An objective check passes | Claude, on its own | "Done when CI is green" |

68| You approve a prepared result | You, one click | "Draft the status memo and post it here for approval" |

69| You choose between options | You, one word | "Research approaches A and B and recommend one" |

70| No verifiable condition exists | No one | Reframe it as a question instead of a task |

7171

7272Two refinements make the table work in practice:

7373

from line 132

132132

133133Channel access belongs to the channel, and DM access belongs to you. A channel can also be yours alone. Create one with just you and Claude in it, and it works the same way a team channel does. The table compares the three surfaces.

134134

135| | A team channel | Your own channel | A DM |

136| :---------------- | :----------------------------------------- | :---------------------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------- |

141| Best for | Shared work the team should see and steer | Your own questions, digests, and follow-ups, kept where a teammate can pick them up | Personal tasks on your own connections, or data that shouldn't run through a shared channel connection |

135| | A team channel | Your own channel | A DM |

136| :- | :- | :- | :- |

142142

143143[Routines](/docs/claude-tag/users/proactivity) belong to a channel too. You set standing work up in the channel where it should post, and it runs with that channel's connections. [Work from your own channel](/docs/claude-tag/users/use-cases/your-own-channel) shows what a channel of your own is good for.

144144

from line 160

160160

161161When Claude gets something wrong, or learns something worth keeping, where you put the fix decides who else benefits and whether you can do it yourself.

162162

164| :---------------------------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------- |

165| How this channel should behave: format, tone, when to respond | [**Channel memory**](/docs/claude-tag/users/memory) (say it and ask Claude to remember) | Anyone in the channel | This channel; the whole workspace only if Claude saves it as a workspace note from a public channel |

166| Conventions and setup for one repository: file layout, PR labels, dependencies to install | **`CLAUDE.md`** at the repo root ([loaded when the repo is](/docs/claude-tag/admins/configure-github#what-loads-from-a-repository)) | Anyone with repo write | Any session that works in that repo, from any channel |

167| Standing rules for this channel that outrank memory | The [**Configure** page](#configure-claude-for-a-channel), in the **Channel instructions** field | Channel members, unless an admin has [restricted it](/docs/claude-tag/admins/attach-to-scope#restrict-who-can-set-channel-instructions) | This channel |

168| How to use a tool correctly, or follow a specific process, org-wide | [**A skill**](/docs/claude-tag/admins/skills-repo) in your org's plugin marketplace | An organization Owner adds it; anyone can ask Claude to open a PR proposing the change | Every channel under the scope it's attached to |

169| Standing rules across many channels | [**Custom instructions**](/docs/claude-tag/admins/attach-to-scope#add-custom-instructions) on a workspace or organization scope | An organization Owner, in the console | Every session in that scope |

164| :- | :- | :- | :- |

170170

171171The first three are yours to write. Skills and wider-scope custom instructions are attached by an Owner, but you can still ask Claude to draft a skill change as a pull request for an admin to review:

172172

claude-tag/users/memory Changed · +4 / -4 lines

from line 22

2222

2323Reading and saving follow different rules depending on where Claude is working:

2424

25| Where Claude is working | Reads from | Saves to |

26| :---------------------- | :--------------------------------------------------------- | :------------------------------------------------------------------------------------------- |

27| Public channel | That channel's notes and the workspace notes | That channel's notes, or the workspace notes for something that applies across the workspace |

28| Private channel | That channel's notes, plus the workspace notes (read-only) | That channel's notes only |

25| Where Claude is working | Reads from | Saves to |

26| :- | :- | :- |

27| Public channel | That channel's notes and the workspace notes | That channel's notes, or the workspace notes for something that applies across the workspace |

28| Private channel | That channel's notes, plus the workspace notes (read-only) | That channel's notes only |

2929

3030Other workspaces stay separate. Direct messages stay separate too. Claude keeps notes for each 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.

3131

claude-tag/users/prompt-library Changed · +11 / -11 lines

from line 152

152152

153153Each entry in the use case library gets one starter here; the linked page has the full setup and the reasoning behind its prompts.

154154

155| To do this | Paste this |

156| :-------------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

157| [Triage requests](/docs/claude-tag/users/use-cases/triage-requests) | "remember for this channel: when someone tags you on a request, check whether it duplicates something already reported, answer it directly if the answer exists, and otherwise route it to the right owner with a one-line summary. Track recurring themes." |

158| [Catch up](/docs/claude-tag/users/use-cases/catch-up) | "what got decided in this thread, and what's still open?" |

159| [Create an artifact](/docs/claude-tag/users/use-cases/create-artifacts) | "turn this thread into a one-page decision doc" |

160| [Track a project](/docs/claude-tag/users/use-cases/track-projects) | "where are we on the migration? What's blocked and on whom?" |

161| [Answer a data question](/docs/claude-tag/users/use-cases/answer-data-questions) | "show signup growth by week, and explain the dips discussed above" |

162| [Find an answer in the docs](/docs/claude-tag/users/use-cases/find-answers) | "what's our policy on data retention, and which doc says so?" |

163| [Pull deal state](/docs/claude-tag/users/use-cases/pull-deal-state) | "what's the state of the Acme renewal?" |

164| [Watch monitors](/docs/claude-tag/users/use-cases/watch-monitors) | "every morning at 7, check the dashboards and post one line per service" |

165| [Fix a bug](/docs/claude-tag/users/use-cases/fix-bugs) | "in acme/data-pipeline, reproduce the bug in this thread, fix it, and open a draft PR" |

155| To do this | Paste this |

156| :- | :- |