Delegate Team Tasks to Claude Inside Slack

Claude Tag is for Claude Team and Enterprise accounts. Anthropic's Claude Tag announcement (https://www.anthropic.com/news/introducing-claude-tag) describes it as a team workflow for Slack, where @Claude can work in a channel and respond back in the thread.

You also need Slack admin permissions so you can install and pair the Slack app.

Pro tip: If you do not have a business plan for Claude, you can still follow along with the regular Claude in Slack (https://claude.com/docs/connectors/slack) experience. That path uses your own Claude account instead of a shared team Claude. But Anthropic says this legacy Claude in Slack experience is being deprecated in August 2026.

In Slack, open Admin > Apps and workflows, search for Claude, and install the app.

You can also open the Claude app in the Slack Marketplace (https://slack.com/marketplace/A08SF47R6P4-claude) directly.

Slack will send you into the browser for most admin actions. That is normal. The Slack desktop app is mostly the starting point; install, permissions, and pairing happen in browser windows.

Back in the Slack app, you should see Claude in your bottom-left sidebar under Apps. Open it, click the Home tab, and connect your Claude account.

Once connected, the app Home tab is also where you will see account details, routing options, and the regular Claude in Slack setup. Claude Tag setup is separate, and happens in the browser.

In your browser, open Claude Tag admin settings (https://claude.ai/admin-settings/claude-tag). You may also see a Claude Tag setup prompt from Claude settings.

Follow the setup flow from Anthropic's setup instructions (https://claude.com/docs/claude-tag/admins/setup-overview):

• Pair Claude Tag with your Slack workspace.
• Connect the tools you want Claude to use.
• Add usage credits and set a spending limit.
• Launch Claude Tag.

Connect only the tools you are comfortable exposing to the channel. In the recording, we tested Google Drive and Notion. Gmail or shared inbox access is more sensitive because anyone in the allowed Slack scope can tag Claude and ask it to use that connection.

Pro tip: Only enable Claude Tag in one test channel first. That gives you a small group of testers, a clear access boundary, and an easier way to watch token spend.

In the Slack channel you want to test, run:

@Claude connect

Claude will return a pairing code. Copy that code into the Claude setup dialog in your browser.

During pairing, choose the narrowest scope that works for your test. For a first run, pick one channel instead of the whole workspace. This keeps Claude away from unrelated channels while you confirm the setup, permissions, and spend behavior.

If your Team plan needs usage credits, Claude will prompt you to add them before launch. Channel work draws from the organization usage balance, not an individual user's normal Claude chat limits.

Before testing, open Advanced in Claude Tag admin settings (https://claude.ai/admin-settings/claude-tag) and switch from the expensive default model to Sonnet.

In our test, the default model burned through usage credits much faster than expected. Sonnet was the safer starting point for a first test.

Then run your first task inside the dedicated Slack thread:

@Claude analyze our brand kit and drafted social posts in Google Drive.
Suggest social strategy improvements.

Claude should reply in the thread, show a short checklist, and keep working in the cloud. You can open the linked Claude session to see more of what it is doing.

The result was not perfect in our demo because the test Drive did not have enough useful files. But the workflow worked: Claude picked up the Slack request, looked through the connected tool, and reported back like a teammate.