Claude Tag is Anthropic’s Slack integration that turns the assistant into a channel participant. Mention @Claude in a connected channel and it runs tasks in an Anthropic-hosted sandbox, posts progress back to the thread, accepts mid-task steering from anyone present, and returns finished work to the conversation. Setup is straightforward in principle but requires careful choices around channel scope, connected tools, model selection, and spend limits before the integration is safe to leave running.
What an admin needs before installation
Claude Tag is not available on Free, Pro, or Max individual plans. It requires a Claude Team or Claude Enterprise plan, Slack workspace admin permissions, and the ability to install Slack apps in the workspace. Admins also need access to the Claude Tag settings at claude.ai/admin-settings/claude-tag as an organization Owner or Admin, funded usage credits on the Team plan, and a dedicated test channel that does not touch live client or production data.
Two policy decisions should be made before the first install: which tools Claude is allowed to reach, and what employees may or may not delegate to it. These choices shape every later step.
How should the Slack install and account pairing actually work?
Install begins at claude.com/claude-for-slack. After clicking Add to Slack and confirming the correct workspace, most workspaces require an admin to approve the app, so admin permissions are effectively mandatory. An earlier “Claude in Slack” app existed before Claude Tag, so confirm the team is installing the current product.
Inside Slack, open the Claude app and then open the Claude Tag admin settings in a browser. Connect only the tools the team plans to delegate work through. There are more than twenty pre-built connectors, including Google Drive, Gmail, Google Calendar, Notion, Confluence, GitHub, GitLab, BigQuery, Snowflake, Linear, Asana, Jira, HubSpot, Salesforce, Datadog, and Sentry, plus custom tools and custom MCP servers via the “Connect another tool” option. Slack channel history, web search, and sandboxed code execution need no extra credentials.
Pairing happens from inside the Slack workspace. An admin posts @Claude connect as a top-level message in the target channel. Claude replies with a single-use pairing code that expires in 15 minutes. Paste that code into the Set up wizard at claude.ai/admin-settings/claude-tag.
The wizard asks for three things. First, a channel scope: Whole workspace or Specific channels. Specific channels with a single test channel is the safer starting point. Second, an access bundle: a named set of tool credentials attached to that scope, so an engineering channel can have GitHub access while a marketing channel only sees documents. Third, a spend limit for the scope. Click Launch to finish.
One rule applies to all later changes: configuration updates such as new tools or settings only affect new threads. An existing thread keeps the connections it started with, which is why testing changes in a fresh thread matters.
Which model should be the default, and how is spend controlled?
Under Customize at claude.ai/admin-settings/claude-tag, set the default model for the scope. Sonnet is a sensible default for summaries, drafts, research, and internal documentation, and it costs meaningfully less per token than Opus. Reserve Opus for high-stakes or genuinely complex work. Users can still switch models inside a thread by asking, for example @Claude use Sonnet for this. The reply footer shows which model answered, which makes per-thread auditing straightforward.
Three habits keep the bill predictable. Use a dedicated test channel so early experiments do not consume credits meant for production. Expand from one channel to more channels slowly, and set a spend limit before launch, not after the first surprise. Review token spend after the first few runs at claude.ai/admin-settings/usage/claude-tag, which resets each billing period. Work done in channels bills to the organization’s shared usage credit balance, while direct messages with Claude bill to the sender’s own seat.
What should a test run actually verify?
Tag @Claude with a simple, real task in the dedicated test channel. A reliable first prompt: @Claude please summarize this thread, identify the open questions, and create a short action list for the team. Confirm four things during the run: Claude responds, it uses the right context, it touches only the tools expected for that task, and it produces output a human would actually use. Only after that review should access expand to more channels.
After the first few tasks, check three things in the admin pages. Token spend per channel on the usage page. Which connected tools were actually used, and drop the ones that are not pulling their weight, tightening the access bundle if Claude is reaching into systems that were not expected. The memory Claude has saved, because Claude Tag keeps persistent, channel-scoped memory. Memory from public channels is shared across the workspace, while memory from private channels stays in that channel. Anyone in the channel can ask @Claude what do you remember about this channel? and can correct or remove entries by talking to Claude. Organization Owners can edit or delete a scope’s memory in admin settings, and Admins can view it. If multiple teams use Claude Tag, schedule a regular memory review.
How should safety and permissions be configured?
Start with limited channel access and expand slowly. Avoid connecting sensitive tools first, especially anything that writes to production systems. Do not give Claude access to private client data without an approved internal policy. Write simple rules for what employees may delegate and which channels Claude is allowed in. Keep a human in the loop on any output that reaches a customer or affects revenue. Monitor usage and costs weekly at first, then monthly once the spend pattern is clear.
Two guest-related behaviors are worth flagging. Slack channels shared across multiple workspaces are not supported. In channels that include guests, Claude stays silent unless the admin enables Allow Claude to respond to guests.
Which use cases fit Claude Tag best?
The integration fits work that already happens in Slack threads: summarizing long threads into decisions and action items, capturing meeting follow-ups, drafting client updates from internal discussions, turning open conversations into structured task lists, researching internal questions across Drive, Notion, Confluence, and the web, creating SOPs from Slack conversations, producing first drafts of blog posts, emails, and reports, running project status reviews across connected tools, preparing sales or support responses from prior context, and organizing team knowledge into searchable documentation.
Practical prompts that copy and paste cleanly into a thread include: @Claude summarize this thread and list the decisions made. @Claude create a task list from this conversation and group it by owner. @Claude turn this discussion into a client-friendly update. @Claude review this idea and identify risks or missing details. @Claude draft an SOP based on the process described in this thread. @Claude create a blog outline from the points above. @Claude compare the options discussed here and recommend the best one. @Claude find the open questions we still need to answer. @Claude rewrite this into a professional email. @Claude create a concise executive summary of this thread.
What are the common setup failures and their fixes?
Most issues fall into a small set of causes. If Claude does not respond, the app may not be installed or approved, the channel may be outside the scope, Claude Tag may be switched off for that scope, or guests in the channel may be blocking the reply. A pairing code that expired or was already used means re-posting @Claude connect and pasting the new code promptly. Only admins can run @Claude connect, which is by design. Usage credits must be funded on Team plans before Claude Tag will run. New tool connections only apply to new threads, so test new settings in a fresh thread. A “Still waiting for available capacity” message is transient and resolves by retrying in the same thread. Higher-than-expected costs point to the default model and the per-channel spend page. Tools being used beyond expectations mean tightening the access bundle for that scope. Memory that needs review or deletion can be edited by Owners in admin settings or corrected by channel members by talking to Claude.
FAQ
What plan is required to install Claude Tag in Slack?
Claude Tag requires a Claude Team or Claude Enterprise plan. It is not available on Free, Pro, or Max individual plans, and the organization must fund usage credits before Claude Tag will run.
How is Claude Tag paired with a Slack channel?
An admin posts @Claude connect as a new top-level message in the target channel. Claude replies with a single-use pairing code that expires in 15 minutes. The code is pasted into the Set up wizard at claude.ai/admin-settings/claude-tag, where the admin selects a channel scope, an access bundle, and a spend limit before clicking Launch.
Where can admins review Claude Tag spend and memory?
Token spend per channel lives at claude.ai/admin-settings/usage/claude-tag and resets each billing period. Channel-scoped memory can be inspected by Admins in admin settings and edited or deleted by Organization Owners, while channel members can correct or remove entries by talking to Claude.