Skip to main content
If your organization already used the earlier Claude in Slack, Claude Tag replaces it in place. Your existing Slack app and @Claude handle stay; there is nothing to reinstall or migrate. What changes is who Claude acts as and who sets it up.

​
Switch your workspace to Claude Tag

1

Connect the workspace in the Claude console

Open claude.ai/admin-settings/claude-tag. If your workspace isn’t paired, run the setup wizard; otherwise you’re already on Claude Tag. Once paired, channels and linked-user DMs answer with the New version by default; no per-channel action is needed.
2

Check for channels still on Legacy

In the Claude Tag’s access section, look at the Claude in Slack version on each scope. Set any showing Legacy to New.
3

Give Claude its connections

The New version starts with no access of its own. Follow the setup overview to add connections and decide which channels can use them.
4

Tell your users

Send them Get started. The visible change is that work now belongs to the channel; see What existing users notice after the switch below.
You’ll see: the workspace appears under Where Claude Tag works, and the Claude in Slack version on each scope shows New.
The earlier Claude in Slack app, shown as Legacy in admin settings, is being deprecated; check with your account team for the cutover date. After that date, channels still set to Legacy stop responding until the scope’s Claude in Slack version is set to New.

​
What stays the same

  • The Slack app and the @Claude handle. There is nothing to reinstall or rename, and your existing Claude in Slack settings (allowed users, verified-domain restriction) carry over. If your earlier install predates a permission Claude now uses, @Claude connect says so when you pair and a Slack admin re-approves the app from the install link; otherwise no app-side action is needed.
  • Direct messages still run on the user’s own claude.ai account, the same way they did before. The shift to a shared identity applies to channels.
  • Users who already linked their claude.ai account keep that connection. It is what powers their DMs.

​
How Claude Tag differs from the earlier app

The earlier app linked each user’s own claude.ai account, so it answered as that person and used their connectors. Claude Tag has one identity for the team, provisioned by an admin, and what it can reach follows the channel.
Legacy (the earlier Claude in Slack)New (Claude Tag)
IdentityEach user links their own claude.ai accountOne agent identity with org-level service credentials
SessionsSpawned per requestOne persistent session per thread, shared with the channel
MemoryNoneShared workspace memory plus private-channel memory
Standing workNoneRoutines and channel watching
Who sets it upEach user, individuallyAn Owner, once
The Claude in Slack version setting on each scope lets you pin a channel or workspace to Off, Legacy, or New, or Inherit the organization default. Use it to hold specific channels on the Legacy behavior while you finish provisioning, then switch them when ready. Access bundles only apply where the New version answers. See the version setting for the control.

​
What existing users notice after the switch

In channels, the visible difference is that work belongs to the channel, not to whoever asked. Anyone can reply in a thread to steer it, and the result stays where the team can see and pick it up. Code work is authored by the Claude GitHub App rather than as the requesting user. A user who never linked a claude.ai account can now hand Claude work in channels, by default. Whether that stays open or narrows to organization members is the admin’s Members choice. If @Claude in a channel still opens pull requests under the asker’s name, that channel is answering with the Legacy version; check the scope’s Claude in Slack version setting.