Claude Tag in Slack is Anthropic's new public-beta experience for assigning work to @Claude in a channel. It replaces the earlier Claude in Slack behavior with a shared, organization-managed agent identity, persistent thread sessions, channel context, connections selected by an owner, and consumption-based channel usage. Anthropic's current support pages say Claude in Slack will switch to Claude Tag on August 3, 2026. Organizations using the earlier integration should inventory access, pair their Slack workspace, provision connections, set spend controls, and test the New version before their own cutover.
Quick Answer
Claude Tag lets people mention @Claude in an approved Slack channel and delegate a task in the conversation where the work is happening. It is in public beta for Claude Team and Enterprise plans. A Claude Primary Owner or Owner—not an Admin—must pair the Slack workspace, choose where Claude works, configure organization-owned connections, set access and spending controls, and test the experience. Existing customers keep the Claude Slack app and @Claude handle, but user-level connectors do not migrate to the new shared identity. Anthropic's public support documentation currently lists August 3, 2026 for the switch, while some earlier workspace notices described a shorter window. Verify the date shown in your own admin console or notice and plan to finish early.
TL;DR
- What changed: In channels, Claude now works as a shared organization identity rather than as the individual user who mentioned it.
- Who is affected: Claude Team and Enterprise organizations using Slack, especially those already using the earlier Claude in Slack or Claude Code in Slack experience.
- What admins must do: Pair the workspace, switch scopes from Legacy to New, re-provision connections, define access boundaries, set spend limits, and run a controlled pilot.
- What stays the same: The Slack app, @Claude handle, and linked-user direct messages remain. Direct messages run on the user's own Claude account.
- Timeline: Anthropic's current public support pages list August 3, 2026. An earlier June 23 notice described retirement 30 days later; workspace-specific timing may differ, so verify your own notice and account guidance.
- Beta warning: Claude Tag is in public beta. Features, controls, and documented behavior may change before general availability.
What Changed With Claude Tag in Slack?
The earlier Claude in Slack connected each person to their own Claude account. Channel responses could use that person's connectors, and work was effectively tied to the requester. Claude Tag changes the operating model: in channels, Claude acts under an organization-managed agent identity. The channel gets a shared thread session that collaborators can continue, and owners decide which tools, repositories, credentials, and memory scopes Claude may use.
That distinction is important. Claude Tag is not simply a new name for the Slack connector. Claude Tag brings Claude into Slack as a shared agent. The Slack connector lets a user working in a Claude app search or reference Slack content under that user's authorized access. Organizations may use both, but they solve different problems.
Anthropic describes several new channel capabilities in the beta:
- A persistent session within each thread, visible and steerable by channel members.
- Shared workspace context and separate private-channel context.
- Scheduled tasks, routines, and proactive follow-up where configured.
- Organization-owned connections to tools and repositories.
- Organization-wide and per-channel spend controls.
- Administrative memory, activity, and network-call review.
Direct messages remain a separate surface. They use the individual user's Claude account and personal tools, while channel work uses the organization's Claude Tag identity and usage balance.
Legacy Claude in Slack vs. Claude Tag
| Area | Earlier Claude in Slack (Legacy) | Claude Tag (New, public beta) | Admin action |
|---|---|---|---|
| Identity | Individual user's linked Claude account | Shared organization agent identity | Assign an owner and document accountability |
| Connections | User's connectors | Organization-owned credentials and repositories | Reconfigure required connections; they do not migrate |
| Session | Created per request | Persistent, shared session per thread | Train users that anyone in the channel can steer the task |
| Memory | No shared Claude Tag memory | Workspace memory plus private-channel memory | Review, edit, and delete memory as needed |
| Standing work | Not supported in the same model | Routines, scheduled work, and channel watching | Approve recurring use cases and owners |
| Setup | Each user linked an account | Primary Owner or Owner configures once | Complete setup before switching scopes to New |
| Channel billing | Individual account behavior | Organization usage balance | Set organization and channel limits before launch |
| Slack surface | Claude app and @Claude handle | Same app and handle | Do not uninstall solely to migrate |
For organizations already using Claude and Slack through MCP, our guide to Claude AI + Slack and the Model Context Protocol explains that separate, user-centered connector pattern.
Who Is Affected?
Claude Tag is currently available in beta to Claude Team and Enterprise customers. The change matters to four groups:
- Claude Primary Owners and Owners must perform the Claude-side setup. Anthropic says the Admin role alone cannot configure Claude Tag's access and channels.
- Slack admins or org owners may need to approve or refresh the Claude app, especially on Enterprise Grid or when newer permissions are required.
- Security, legal, and data-governance teams need to review shared identity, channel memory, tools, credentials, logs, retention, and cross-channel boundaries.
- Channel users need to understand that work is shared, channel-visible, and potentially persistent. A task should not include secrets or data that the channel and configured tools are not approved to handle.
Organizations not using the prior integration still need an admin-led setup. Organizations using Legacy have an additional migration requirement because prior user connections do not become Claude Tag's organization-owned connections.
What Admins Should Do Now
Treat the migration as a small production rollout, not a toggle change. The same disciplines used in Claude AI consulting and implementation—readiness, architecture, governance, adoption, and measurement—apply here.
1. Confirm ownership, plan eligibility, and your deadline
Identify the Claude Primary Owner or Owner who will configure Claude Tag and the Slack administrator who can approve app changes. Confirm that the organization is on a supported Team or Enterprise plan. Check the date in the Claude admin console, workspace notice, and account-team guidance rather than assuming every organization shares the same transition date.
2. Inventory current Slack use
List the workspaces and channels using @Claude today. Record which users rely on personal connections, which repositories or tools are needed, which channels contain sensitive data, and which workflows must continue after cutover. Do not assume a user connector, repository authorization, or history will migrate.
3. Pair the Slack workspace in Claude
A Claude Primary Owner or Owner should open Organization settings → Claude Tag and run the setup wizard if the workspace is not already paired. Existing customers keep the same Slack app and @Claude handle. If an Enterprise Grid installation has lost its connection, follow Anthropic's migration troubleshooting rather than uninstalling the app.
4. Provision organization-owned connections
Claude Tag's New version starts without the user's former connectors. Add only the repositories, tools, and credentials required for the pilot. Define access at the correct level:
- Organization: access needed wherever Claude Tag operates.
- Workspace: access for public channels in that Slack workspace.
- Private channel: additional tools and memory isolated to a smaller group.
Use least privilege, separate high-sensitivity use cases, and avoid giving broad credentials to a general-purpose workspace scope. If this requires redesigning permissions or data flows, system integration and data migration services can help establish durable boundaries.
5. Restrict who can use Claude Tag
Review the member-access control before rollout. Anthropic currently documents different controls for Team and Enterprise, with role-based restrictions available on Enterprise. Pay attention to the default: depending on configuration, people in the paired Slack workspace may be able to use Claude in approved channels even without being a member of the Claude organization.
Also decide where Claude may operate. Start with a small number of low-risk channels. For a phased migration, scopes can remain on Legacy while provisioning is completed, then move to New. Setting a scope to Off disables both versions there.
6. Fund and cap channel usage
Channel work is consumption-based and bills to the organization's usage balance; direct messages bill to the user's own Claude account. Team organizations need a funded usage balance before Claude can work in channels. Enterprise invoiced organizations should still set a pilot cap.
Configure an organization-wide spend limit, per-channel limits, and alert ownership. Anthropic documents notifications at 75% and 95% of a limit and a per-channel usage breakdown. A spend limit is not a throughput limit, so track rate-limit messages separately.
7. Switch test scopes to New and validate
In Claude Tag's access, check each scope's version. Pairing should default scopes to New, but any channel showing Legacy must be changed when ready. Validate at least these cases:
- @Claude responds in an approved channel and stays silent where disabled.
- A permitted user can start and continue a task; a restricted user cannot.
- The task uses only approved connections and repositories.
- Private-channel context does not surface in public-channel work.
- The response and any external action are attributable to Claude's identity.
- Memory and audit views show expected activity.
- Organization and channel spend controls behave as designed.
- A direct message still uses the user's personal Claude account as expected.
8. Communicate the operating model
Tell users what changed, where Claude is approved, what information is prohibited, how shared threads work, who owns recurring tasks, and where to report a problem. Update runbooks and onboarding. Strong rollout communication is part of advisory and change management, not an afterthought.
Migration Checklist
- [ ] Name a Claude Owner and Slack admin for the migration.
- [ ] Confirm Team or Enterprise eligibility and the workspace-specific deadline.
- [ ] Inventory active channels, workflows, repositories, and user connectors.
- [ ] Classify sensitive channels and exclude them from the initial pilot.
- [ ] Pair the Slack workspace in Claude Tag settings.
- [ ] Recreate required connections under the organization identity.
- [ ] Configure member restrictions and channel scopes.
- [ ] Fund usage if required and set organization/per-channel limits.
- [ ] Switch pilot scopes from Legacy to New.
- [ ] Test access, memory, audit logs, spend behavior, and failure handling.
- [ ] Train users on shared channel work versus personal direct messages.
- [ ] Monitor the pilot, document findings, and expand in stages.
Timeline and Date Caveat
Anthropic announced Claude Tag on June 23, 2026 and said existing Claude in Slack customers should opt in within 30 days. A notice sent that day can therefore be read as pointing to approximately July 23, 2026. However, Anthropic's current public support articles now state that Claude in Slack will switch to the new Claude Tag experience on August 3, 2026. The detailed migration documentation also advises customers to check with their account team for the Legacy cutover date.
The prudent interpretation is:
- Use August 3, 2026 as the current public documentation date.
- Treat any date in your organization's console, email notice, or account-team communication as workspace-specific guidance.
- Complete setup and testing before the earlier applicable date; do not wait for automatic switching.
- Recheck Anthropic's documentation because the product is in public beta and details can change.
Some organizations may receive separate promotional terms for launch usage. Those terms are account-specific, are not part of the public product specification, and should be verified in the recipient organization's own notice and billing console.
FAQ
Is Claude Tag generally available?
No. Anthropic labels Claude Tag as a public beta for Team and Enterprise plans. Features and behavior may change before general availability.
Do we need to install a different Slack app?
Existing customers generally keep the same Claude app and @Claude handle. Anthropic's migration guide says not to uninstall the app merely to migrate. A Slack administrator may need to approve updated permissions or refresh an Enterprise Grid connection in place.
Do our existing Claude connectors and repositories migrate?
No. Anthropic says the New version begins without access of its own. User-linked GitHub repositories and other connections do not carry over to the shared organization identity. Owners must configure the required connections for Claude Tag.
Who can set up Claude Tag?
A Claude Primary Owner or Owner configures Claude Tag's access and channels. Anthropic explicitly states that the Claude Admin role alone cannot perform that setup. Slack approval may also require a Slack admin or org owner.
How does Claude Tag billing work?
Work performed after an @Claude mention in a channel uses the organization's usage balance and is consumption-based. Direct messages use the individual's Claude account. Owners can set organization-wide and per-channel spending limits and review channel-level usage.
Can anyone in Slack use Claude Tag?
That depends on the member-access setting. Anthropic documents controls that can allow anyone in the connected Slack workspace, restrict access to members of the Claude organization, or use Enterprise role-based access. Review the default before enabling broad channel access.
What happens to channel history and memory?
Claude Tag maintains shared workspace memory and separate private-channel memory for its work. Admins can review, edit, and delete memory. Slack messages remain subject to the organization's Slack retention policy; Claude's separate handling and deletion rules should also be included in the governance review.
Which migration date should we follow: July 23 or August 3?
Anthropic's current public support articles list August 3, 2026. The approximately July 23 date comes from applying a 30-day window to the June 23 announcement or an earlier notice. Follow the date shown for your workspace and confirm it with your account team if the sources differ. Finish migration testing before the earlier date when practical.
Plan a Governed Claude Tag Rollout
Claude Tag changes identity, permissions, cost ownership, and team behavior at the same time. Vantage Point helps organizations turn that change into a controlled rollout: map use cases, design least-privilege access, configure integrations, set governance and spend controls, run pilot testing, and train the teams who will use @Claude.
Start with a focused Claude AI readiness and implementation conversation, or contact Vantage Point to review your Slack migration plan, security requirements, and adoption timeline.
