Work with Claude Tag changedclaude-tag/overview
Nearest release: v2.1.290, published under an hour before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 5 Oct 2026 18:53 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 22 Oct 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+33added
Lines−33removed
From line
33
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits19to this page, all time
The whole hunk
from line 33, old and new numbered
/
from line 33
3333
3434Claude 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. To use it, your organization pairs its Slack workspace with its Claude organization; see [the setup overview](/docs/claude-tag/admins/setup-overview) for the full prerequisites.
3535
36If you're choosing between Claude products for Slack-shaped work, [how Claude Tag differs from Cowork and Claude Code](/docs/claude-tag/concepts/how-it-works#how-claude-tag-differs-from-cowork-and-claude-code) compares them directly: team work in shared channels is Claude Tag; personal work on your own files is Cowork or Claude Code.
36If you're choosing between Claude products for Slack-shaped work, [how Claude Tag differs from Cowork and Claude Code](/docs/claude-tag/concepts/how-it-works.md#how-claude-tag-differs-from-cowork-and-claude-code) compares them directly: team work in shared channels is Claude Tag; personal work on your own files is Cowork or Claude Code.
3737
3838### Who needs a Claude seat
3939
4040Slack users don't each need a Claude seat to work with Claude in channels.
4141
42* **In channels**: by default, anyone in the paired Slack workspace can tag `@Claude` in a channel, and an Owner can [restrict who can use Claude](/docs/claude-tag/admins/restrict-access#restrict-who-can-use-claude) to people in your Claude organization or, on Enterprise, to specific roles. Channel work bills by usage to your organization's usage balance, under a [spend limit](/docs/claude-tag/admins/set-spend-limit) an Owner sets.
43* **In group DMs**: the same restriction on who can use Claude applies, and the work bills to your organization's usage balance. See [Group DMs](/docs/claude-tag/admins/restrict-access#group-dms).
44* **In one-to-one DMs**: a DM from a member who has connected a Claude account runs on that account and bills to that person's seat. The seat must include Claude Code, or, on the Enterprise plan, be a **Standard** or **Usage-Based Chat** seat held by someone who also has Cowork. A [DM from a member who hasn't connected a Claude account](/docs/claude-tag/admins/restrict-access#direct-messages-from-members-without-a-claude-account) can bill to your organization for a limited time.
42* **In channels**: by default, anyone in the paired Slack workspace can tag `@Claude` in a channel, and an Owner can [restrict who can use Claude](/docs/claude-tag/admins/restrict-access.md#restrict-who-can-use-claude) to people in your Claude organization or, on Enterprise, to specific roles. Channel work bills by usage to your organization's usage balance, under a [spend limit](/docs/claude-tag/admins/set-spend-limit.md) an Owner sets.
43* **In group DMs**: the same restriction on who can use Claude applies, and the work bills to your organization's usage balance. See [Group DMs](/docs/claude-tag/admins/restrict-access.md#group-dms).
44* **In one-to-one DMs**: a DM from a member who has connected a Claude account runs on that account and bills to that person's seat. The seat must include Claude Code, or, on the Enterprise plan, be a **Standard** or **Usage-Based Chat** seat held by someone who also has Cowork. A [DM from a member who hasn't connected a Claude account](/docs/claude-tag/admins/restrict-access.md#direct-messages-from-members-without-a-claude-account) can bill to your organization for a limited time.
4545
4646## Where Claude Tag runs
4747
4848Claude Tag works in Slack. You interact with it by writing in a Slack channel, thread, or direct message, and it replies there. Mention `@Claude` in a channel to guarantee it picks the message up.
4949
50When Claude works on a task, it runs in an ephemeral sandbox, not on your computer. The sandbox is created when a conversation starts, holds any code or files Claude is working with, and is discarded when the conversation goes idle. See [how Claude Tag works](/docs/claude-tag/concepts/how-it-works) for the full lifecycle.
50When Claude works on a task, it runs in an ephemeral sandbox, not on your computer. The sandbox is created when a conversation starts, holds any code or files Claude is working with, and is discarded when the conversation goes idle. See [how Claude Tag works](/docs/claude-tag/concepts/how-it-works.md) for the full lifecycle.
5151
52You extend what Claude can reach, like your repositories, ticketing systems, data warehouses, and custom tools, through [Claude Tag connectors](/docs/claude-tag/admins/add-connections), [plugins, and skills](/docs/claude-tag/admins/customize). An Owner or a [Claude Tag admin](/docs/claude-tag/admins/restrict-access#delegate-claude-tag-administration) configures these for all of Slack, for one workspace, or for one channel. Members' own claude.ai connectors are separate from that configuration; Claude can use them in a channel for the member's own requests, as [personal connectors in channels](/docs/claude-tag/concepts/personal-connectors) describes.
52You extend what Claude can reach, like your repositories, ticketing systems, data warehouses, and custom tools, through [Claude Tag connectors](/docs/claude-tag/admins/add-connections.md), [plugins, and skills](/docs/claude-tag/admins/customize.md). An Owner or a [Claude Tag admin](/docs/claude-tag/admins/restrict-access.md#delegate-claude-tag-administration) configures these for all of Slack, for one workspace, or for one channel. Members' own claude.ai connectors are separate from that configuration; Claude can use them in a channel for the member's own requests, as [personal connectors in channels](/docs/claude-tag/concepts/personal-connectors.md) describes.
5353
5454For administrators
5555Set up Claude Tag
from line 62
6262Pair your Slack workspace, launch, and test that it works](/docs/claude-tag/admins/setup-overview)
6363
6464[What can Claude Tag access?
65How admins set access per channel, and where credentials are stored](/docs/claude-tag/concepts/agent-identity)
65How admins set access per channel, and where credentials are stored](/docs/claude-tag/concepts/agent-identity.md)
6666
6767[How do I connect each service?
68Credential types, allowed hosts, and what each connection lets Claude reach](/docs/claude-tag/admins/add-connections)
68Credential types, allowed hosts, and what each connection lets Claude reach](/docs/claude-tag/admins/add-connections.md)
6969
7070For end users
7171Put Claude Tag to work
from line 75
7575[Open](#put-claude-tag-to-work)
7676
7777[How do I hand Claude Tag a task?
78Mention Claude in any channel it's in, with nothing to install](/docs/claude-tag/users/getting-started)
78Mention Claude in any channel it's in, with nothing to install](/docs/claude-tag/users/getting-started.md)
7979
8080[What is Claude Tag good at?
81Use cases for coding, data, incidents, and go-to-market](/docs/claude-tag/users/use-cases)
81Use cases for coding, data, incidents, and go-to-market](/docs/claude-tag/users/use-cases.md)
8282
8383[How do I get good results?
84Good habits for scoping and reviewing work](/docs/claude-tag/users/good-habits)
84Good habits for scoping and reviewing work](/docs/claude-tag/users/good-habits.md)
8585
8686[What does Claude Tag remember?
87Channel memory, what's shared across the workspace, and who can see what](/docs/claude-tag/users/memory)
87Channel memory, what's shared across the workspace, and who can see what](/docs/claude-tag/users/memory.md)
8888
8989[Can Claude Tag run tasks on a schedule?
90Scheduled jobs, channel watching, and triggers](/docs/claude-tag/users/proactivity)
90Scheduled jobs, channel watching, and triggers](/docs/claude-tag/users/proactivity.md)
9191
9292## Billing and spend limits
9393
94Adding Claude to Slack doesn't add a per-seat charge. Channel, thread, and group DM work is billed by usage instead: it draws from a **usage balance**, an amount in your organization's billing currency that an Owner funds. A [spend limit](/docs/claude-tag/admins/set-spend-limit) caps how much of that balance Claude Tag can use each billing period.
94Adding Claude to Slack doesn't add a per-seat charge. Channel, thread, and group DM work is billed by usage instead: it draws from a **usage balance**, an amount in your organization's billing currency that an Owner funds. A [spend limit](/docs/claude-tag/admins/set-spend-limit.md) caps how much of that balance Claude Tag can use each billing period.
9595
96One-to-one direct messages from members who have connected a Claude account don't draw from this balance. Such a DM runs on the sender's own claude.ai account and follows that seat's usual usage limits, so the organization spend limit doesn't apply to it. A [DM from a member who hasn't connected a Claude account](/docs/claude-tag/admins/restrict-access#direct-messages-from-members-without-a-claude-account) can draw from this balance.
96One-to-one direct messages from members who have connected a Claude account don't draw from this balance. Such a DM runs on the sender's own claude.ai account and follows that seat's usual usage limits, so the organization spend limit doesn't apply to it. A [DM from a member who hasn't connected a Claude account](/docs/claude-tag/admins/restrict-access.md#direct-messages-from-members-without-a-claude-account) can draw from this balance.
9797
98To learn what your team's usage costs, run a pilot with a spend limit set and watch the per-channel breakdown on the [usage page in your admin settings](https://claude.ai/admin-settings/usage/claude-tag). [Set a spend limit](/docs/claude-tag/admins/set-spend-limit) covers how to fund the balance on each plan, set the limit, and what happens when usage reaches it.
98To learn what your team's usage costs, run a pilot with a spend limit set and watch the per-channel breakdown on the [usage page in your admin settings](https://claude.ai/admin-settings/usage/claude-tag). [Set a spend limit](/docs/claude-tag/admins/set-spend-limit.md) covers how to fund the balance on each plan, set the limit, and what happens when usage reaches it.
9999
100100For end users
101101
from line 103
103103
104104If Claude Tag is in your channel, you can use it now. (If it isn't there yet, an Owner in your Claude organization runs setup: see [Set up Claude Tag](/docs/claude-tag/admins/setup-overview).) Anyone in the channel can hand it work, and channel work bills to the organization, not to you.
105105
106What it can reach starts with the channel you're in. The fastest way to find out is to ask it: `@Claude what can you access from this channel?` Or, if you're signed in to your Claude organization, click **Configure** in the footer of a Claude reply in the channel to see its [connections](/docs/claude-tag/concepts/glossary#connection), the external services an admin has connected for that channel. Replies in org-shared channels have no Configure link.
106What it can reach starts with the channel you're in. The fastest way to find out is to ask it: `@Claude what can you access from this channel?` Or, if you're signed in to your Claude organization, click **Configure** in the footer of a Claude reply in the channel to see its [connections](/docs/claude-tag/concepts/glossary.md#connection), the external services an admin has connected for that channel. Replies in org-shared channels have no Configure link.
107107
108For your own requests, Claude can also [use the connectors on your claude.ai account](/docs/claude-tag/concepts/personal-connectors), after you allow it.
108For your own requests, Claude can also [use the connectors on your claude.ai account](/docs/claude-tag/concepts/personal-connectors.md), after you allow it.
109109
110In a one-to-one DM, Claude runs on your own claude.ai account instead of a channel's setup. An Owner can turn off DMs for the whole organization; see [Allow or disable direct messages](/docs/claude-tag/admins/restrict-access#allow-or-disable-direct-messages).
110In a one-to-one DM, Claude runs on your own claude.ai account instead of a channel's setup. An Owner can turn off DMs for the whole organization; see [Allow or disable direct messages](/docs/claude-tag/admins/restrict-access.md#allow-or-disable-direct-messages).
111111
112112### Common uses
113113
114114Each link opens a guide with the prompts to paste and the connections the task needs.
115115
116* [Watch monitors and alerts](/docs/claude-tag/users/use-cases/watch-monitors): scheduled dashboard checks, and alerts investigated as they arrive. Needs a monitoring connection like Datadog, Sentry, or PagerDuty.
117* [Triage requests](/docs/claude-tag/users/use-cases/triage-requests): an intake channel where Claude answers what it can, flags duplicates, and routes the rest. Works on Slack content alone.
118* [Find answers in your docs](/docs/claude-tag/users/use-cases/find-answers): policy and runbook questions answered with the source. Needs a docs connection like Google Drive, Notion, or Confluence.
119* [Answer data questions](/docs/claude-tag/users/use-cases/answer-data-questions): a plain-language question becomes a warehouse query and a chart. Needs a data warehouse connection.
120* [Track projects and chase approvals](/docs/claude-tag/users/use-cases/track-projects): standing status digests and follow-ups that run until an approval lands
121* [Turn threads into docs and tickets](/docs/claude-tag/users/use-cases/create-artifacts): a settled discussion becomes the decision doc, the customer reply, or the filed tickets
122* [Fix bugs](/docs/claude-tag/users/use-cases/fix-bugs): a bug reported in the channel comes back as a draft pull request. Needs GitHub.
123* [Work from your own channel](/docs/claude-tag/users/use-cases/your-own-channel): scratch questions, digests of channels you don't follow, and follow-ups on what you said you'd do
116* [Watch monitors and alerts](/docs/claude-tag/users/use-cases/watch-monitors.md): scheduled dashboard checks, and alerts investigated as they arrive. Needs a monitoring connection like Datadog, Sentry, or PagerDuty.
117* [Triage requests](/docs/claude-tag/users/use-cases/triage-requests.md): an intake channel where Claude answers what it can, flags duplicates, and routes the rest. Works on Slack content alone.
118* [Find answers in your docs](/docs/claude-tag/users/use-cases/find-answers.md): policy and runbook questions answered with the source. Needs a docs connection like Google Drive, Notion, or Confluence.
119* [Answer data questions](/docs/claude-tag/users/use-cases/answer-data-questions.md): a plain-language question becomes a warehouse query and a chart. Needs a data warehouse connection.
120* [Track projects and chase approvals](/docs/claude-tag/users/use-cases/track-projects.md): standing status digests and follow-ups that run until an approval lands
121* [Turn threads into docs and tickets](/docs/claude-tag/users/use-cases/create-artifacts.md): a settled discussion becomes the decision doc, the customer reply, or the filed tickets
122* [Fix bugs](/docs/claude-tag/users/use-cases/fix-bugs.md): a bug reported in the channel comes back as a draft pull request. Needs GitHub.
123* [Work from your own channel](/docs/claude-tag/users/use-cases/your-own-channel.md): scratch questions, digests of channels you don't follow, and follow-ups on what you said you'd do
124124
125[Get started](/docs/claude-tag/users/getting-started) covers your first message, what you see while Claude works, and how to shape Claude's behavior in your channel.
125[Get started](/docs/claude-tag/users/getting-started.md) covers your first message, what you see while Claude works, and how to shape Claude's behavior in your channel.
126126
127127For administrators
128128
from line 135
135135
136136Once you launch, everyone in a channel Claude is in can use Claude Tag immediately, with no per-user setup.
137137
138Claude Tag starts with no access of its own to your external systems. After you launch, you connect the services Claude will work in, such as your issue tracker or data warehouse, and grant repositories to the Claude GitHub App. Members can also let Claude use their own [personal connectors](/docs/claude-tag/concepts/personal-connectors) for their requests.
138Claude Tag starts with no access of its own to your external systems. After you launch, you connect the services Claude will work in, such as your issue tracker or data warehouse, and grant repositories to the Claude GitHub App. Members can also let Claude use their own [personal connectors](/docs/claude-tag/concepts/personal-connectors.md) for their requests.
139139
140140[Set up Claude Tag](/docs/claude-tag/admins/setup-overview) walks through setup and connecting tools, with what to have ready, what each choice means, and how to verify Claude Tag works once you launch.
141141
142142Security review
143[Security and data handling](/docs/claude-tag/concepts/security-and-data)
143[Security and data handling](/docs/claude-tag/concepts/security-and-data.md)
144144
145145The security model, what admins can and can't restrict, audit trails, and network requirements.
146146
from line 150
150150>
151151> Admins: pair your Slack workspace and launch
152152
153> **[Hand Claude Tag your first task](/docs/claude-tag/users/getting-started)**
153> **[Hand Claude Tag your first task](/docs/claude-tag/users/getting-started.md)**
154154>
155155> It's already in your channel: send your first message
156156
157> **[How Claude Tag works](/docs/claude-tag/concepts/how-it-works)**
157> **[How Claude Tag works](/docs/claude-tag/concepts/how-it-works.md)**
158158>
159159> The session model, what it can read, and how memory follows places
160160
161> **[Use case library](/docs/claude-tag/users/use-cases)**
161> **[Use case library](/docs/claude-tag/users/use-cases.md)**
162162>
163163> Prompts to paste, by team and connection
164164
No line in this hunk matches that.