Skip to main content
If your organization already used the earlier Claude in Slack, including Claude Code in Slack, Claude Tag replaces it. Your existing Slack app and @Claude handle stay, and no data migrates. What changes is who Claude acts as and who sets it up.
If your Team plan organization has the single Respond in channels switch, it has no Claude Tag version controls and there is nothing to migrate.

​
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 setup; 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

Pairing defaults every workspace and channel to New, so this is usually quick.
  1. Go to Claude’s access > Channels. A workspace or channel set to Legacy shows legacy Claude in Slack in the Changes from defaults column.
  2. Open each one, and on its Advanced tab set Claude Tag version to New.
  3. The Slack row never shows that marker, so also go to Claude’s access > Channels > Slack and set Claude Tag version on its Advanced tab to New if it shows Legacy.
3

Give Claude its connections

The New version starts with no access of its own. GitHub repositories and other connections do not carry over from individual users’ linked accounts, so code requests in a switched channel have nothing to clone until you configure them. Follow the setup overview to add connections, and GitHub access for code work specifically.If your teams keep custom skills in a repository’s .claude/skills/ folder, those skills apply only in threads that have the repository. Add the repository to a bundle that applies to the channel, and have users name it in the first message. To give skills to every channel in a workspace or in all of Slack, add them through a skills repository.
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 under Connected workspaces on the Slack page, New as the Slack page’s Claude Tag version, and no row on the Channels tab showing legacy Claude in Slack.

​
If @Claude doesn’t respond at all

On Enterprise Grid, an earlier install can lose its connection and stop responding in every workspace. See Claude is silent everywhere on Enterprise Grid for the reinstall that refreshes it without uninstalling, then send @Claude connect again in a channel of that workspace and pair the workspace with the new code.
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 their Claude Tag version is set to New.

​
What stays the same

  • The Slack app and the @Claude handle. 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; a Slack admin clicks the install link in that reply and approves the consent screen, which installs over the existing app. Otherwise no app-side action is needed.
  • One-to-one 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 who also sets what it can reach in each channel. The Claude Tag version setting on each workspace’s and channel’s page chooses whether the New or Legacy version answers there, and the page’s enable switch turns both off. Bundles only apply where the New version answers. See Turn Claude Tag on or off and set the version for a scope for both controls and where to set them.

​
Two versions of the same Slack app

The earlier Claude in Slack and Claude Tag are two versions of the same @Claude Slack app, not two apps, so there is nothing to uninstall. You choose which version answers in each workspace and channel with the Claude Tag version setting (New, Legacy, or Inherit), so one workspace can run both during a phased switch. Turning off a workspace’s or channel’s enable switch silences both versions there. To keep the earlier behavior in a workspace or channel, set its Claude Tag version to Legacy. To tell which version answered in a channel, look at who authored the work. The New version authors code as the Claude GitHub App and keeps work in the channel’s thread; if @Claude still opens pull requests under the asker’s name, that channel is answering with the Legacy version.

​
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 access restriction setting.