Set up and run Claude Tag in Slack

Claude Tag is available in beta to Claude Enterprise and Team customers. Confirm your plan before starting setup so you are not blocked partway through.

1. Check your current Claude plan under your organization's billing or account settings.
2. If you are not currently on Enterprise or Team, contact your Anthropic account representative or sales to upgrade before continuing.
3. Confirm you have administrator permissions on the Slack workspace you intend to connect, since pairing requires workspace-level approval.

Pairing connects your Slack workspace to your Claude organization so Claude can be invited into channels.

1. Open the Claude Tag admin settings page from your Claude Enterprise or Team dashboard.
2. Select Pair with Slack and choose the workspace you want to connect.
3. Approve the requested Slack permissions when prompted. These permissions let Claude read and post in the channels it is later invited to.
4. Confirm the pairing shows as Connected on the admin settings page before moving to the next step.

This step defines what Claude can see and do. Treat each channel as its own scoped identity, memories and tool access do not cross between channels.

1. From the admin settings page, select the channels you want Claude Tag to operate in.
2. For each channel, choose which tools, data sources, and codebases Claude should be able to access while working there.
3. Keep sensitive data scoped narrowly. A channel set up for sales should not also carry engineering tools or codebases, and the reverse is true as well.
4. Decide whether to enable ambient behavior for each channel. With it on, Claude proactively flags relevant updates and follows up on stalled threads without being tagged first.
5. Save your access configuration.

Spend limits give you a budget ceiling at two levels, the organization as a whole and individual channels, so usage cannot run away unnoticed.

1. In the admin settings page, locate the Spend limits section.
2. Set an organization-wide monthly token spend cap.
3. Optionally set tighter per-channel limits for high-traffic or experimental channels.
4. Save your limits. You can revisit and adjust these at any time as usage patterns become clearer.

Always confirm the setup works in a low-stakes channel before rolling it out to the wider team.

1. Create or choose a private Slack channel for testing.
2. Invite Claude into the channel the same way you would invite a teammate.
3. Tag @Claude with a simple, low-risk request to confirm it responds correctly and has access to the tools you configured.
4. Review the response in the thread and confirm Claude used only the tools and data sources you intended to grant.
5. Once confirmed, the channel is ready for production use, or you can invite Claude into your real working channels.

Claude Tag replaces the existing Claude in Slack app. If your organization already uses it, migration is opt-in rather than automatic.

1. Check whether your workspace currently has the Claude in Slack app installed.
2. If it does, opt in to migration from the Claude Tag admin settings page within 30 days of setting up Claude Tag.
3. Check your eligibility for the introductory launch credit issued to qualifying Enterprise and Team organizations, so your team can try Claude Tag at no additional cost during rollout.

Once testing confirms the setup, open Claude Tag up to the rest of the channel and start using it day to day.

1. Announce Claude Tag in each relevant channel so teammates know it is available and what it has access to.
2. Share a couple of example requests so the team sees how to phrase a task for @Claude.
3. Encourage teammates to tag Claude for things like chasing down product metrics, working through support tickets, or finding the root cause of a bug.
4. Remind the team that direct messages to Claude are answered privately, using each person's own connected tools.
5. Review the admin activity log periodically to see what Claude has worked on and who requested each task.