How Claude Tag Works Inside Your Slack Channels
Claude Tag lets your whole Slack team tag @Claude into a thread, track its progress, and steer it together in real time.
Claude TagSlack Channels
Appearance
How to Set Up Claude Tag in Slack: Step-by-Step Guide
A clear walkthrough of pairing Slack, granting Claude access to your tools, setting a spend limit, and testing the setup.
Your team already lives in Slack. Tickets get discussed there, incidents get triaged there, and decisions quietly disappear into scroll history there too. Adding an AI assistant sounds great in theory, but most setup guides bury you in jargon before you even connect anything.
Claude Tag brings Claude directly into your Slack channels, with access to the tools your team actually uses like GitHub, Linear, BigQuery, or Datadog. The setup has four parts: pairing your workspace, granting access, setting a budget, and testing it works.
This guide walks through each part in plain language, so you can get Claude running in a single pilot channel today.
What You Need Before Starting
You need three things lined up before you touch any settings.
| You need | Why | If you don't have it |
|---|---|---|
| Owner role in Claude org | Only Owners can pair a workspace and create Access bundles | Ask your Owner, or get promoted at claude.ai/admin-settings/members |
| Slack workspace admin | Connecting and installing usually needs admin approval | Send them the install request (template below) |
| Usage credits (Team plans) | Nothing runs until credits are loaded | Buy credits at claude.ai/admin-settings/usage |
A test channel is optional but helpful. Either spin up a private channel or reuse one you already have.
Step 1: Pair Your Slack Workspace
Pairing connects your Slack workspace to your Claude organization. It takes three moves: install the app, grab a code, paste the code.
Install the app
Go to claude.com/claude-for-slack, click Add to Slack, and approve the permissions. Skip this if it's already installed.
Get the pairing code
In any Slack channel or DM, run:
@Claude connectClaude replies with a code. Only a Slack workspace admin can run this command. If that's not you, send this to your admin:
text
Please install the Claude app (https://claude.com/claude-for-slack) in [workspace],
then run "@Claude connect" in any channel and send me the code it returns.Paste the code in Claude's console
Head to claude.ai/admin-settings/claude-tag, click Set up, paste the code, and choose whether Claude should work across the whole workspace or just specific channels.
That's it. Your workspace now shows as connected.
Common pairing problems
| Problem | Fix |
|---|---|
@Claude doesn't respond at all | Have a Slack Org Owner reinstall via "Install to entire organization" at claude.com/claude-for-slack. Don't uninstall first. |
| "Installation is out of date" | A Slack admin clicks the reinstall link in Claude's reply, approves the new permission, then runs @Claude connect again. |
| "Already connected to a different organization" | An Owner in the org that holds the pairing needs to disconnect it first. Check if you have multiple Claude orgs. |
| "Claim code is invalid or expired" | Codes are single-use and expire fast. Just run @Claude connect again for a fresh one. |
Step 2: Give Claude Access to Your Tools
Pairing connects Slack. It doesn't connect anything else. For Claude to read your GitHub repos or query your data warehouse, you create an Access bundle, basically a named set of credentials Claude can use in specific channels.
If you used the setup wizard, it already created a bundle called "Slack default." You're just adding connections to it.
Creating a bundle manually
- Go to claude.ai/admin-settings/claude-tag
- Under Claude Tag's access, pick a scope, click + next to Access bundles, choose Create new bundle
- Rename it to describe what it grants, not which team owns it
Good names: data-readonly, github-write, monitoring. These names stay clear even when multiple teams share the same bundle.
Why split access into multiple bundles
One bundle per capability lets you mix and match per channel:
#platform-eng → data-readonly + github-write + monitoring
#gtm-analytics → data-readonly only
#incidents → monitoring + github-writeRotate a key once, and every bundle using it updates automatically.
What to connect
| Category | Examples | Access level | What it unlocks |
|---|---|---|---|
| Docs | Google Drive, Notion, Confluence | Read | Answers grounded in real docs |
| Code | GitHub, GitLab | Read/write | PRs, branches, CI follow-up |
| Data | BigQuery, Snowflake, Redshift | Read | Charted answers to data questions |
| Monitoring | Sentry, Datadog, PagerDuty | Read | Debugging and incident context |
| Tickets | Linear, Asana, Jira | Read/write | Filing and updating tickets |
| Go-to-market | HubSpot, Salesforce, Gong | Read | Pipeline and account context |
Use a dedicated account, not your own
Never connect your personal login. Create a separate identity for Claude in each tool.
| Service type | Pattern |
|---|---|
| Google Workspace | A virtual user like claude@company.com, scoped to specific folders/calendars |
| Datadog, Snowflake, Sentry | A service account scoped to read-only |
| Linear, Asana | A dedicated user seat with its own access token |
| AWS, GCP | A narrow IAM principal |
This keeps Claude's activity separately auditable, and you can revoke it without touching anyone else's account.
Step 3: Set a Spend Limit
Claude Tag bills against your organization's usage balance, not individual seats. DMs (which run on your personal connectors instead of the team's) are billed separately to the person's own account.
| Plan | What you must do |
|---|---|
| Team | Required. Buy credits first, nothing runs until you do |
| Enterprise (invoiced) | Recommended. No cap by default |
To set it: go to claude.ai/admin-settings/usage/claude-in-slack and enter an amount in your billing currency. It resets every billing period and applies across all paired workspaces.
When the limit is hit, Claude stops mid-task and tells the requester in the thread. They can ask an admin to raise it.
Step 4: Test the Setup
Don't roll this out to the whole company yet. Test in one channel first.
Test 1: Basic functionality
/invite @Claude
@Claude summarize what this channel decided this week and list any open questionsThis only uses Slack history, so it confirms the install and connection work, no external tools involved (to learn how to frame tasks so they can actually finish, see our task-tagging guide).
Passed when Claude shows "is thinking…" and posts a real summary.
Test 2: Each connection
For every tool you connected:
@Claude what can you access from this channel?Then ask for something simple, like the latest tickets from your issue tracker. Check that the action shows up in that tool's own audit log under the service account you created.
If something fails
| Symptom | Likely cause |
|---|---|
| No response at all | The channel isn't covered by any scope yet |
| Responds but can't reach a connected tool | Connections only apply to new threads, start a fresh one |
| Error message | It names what's missing, fix that specific piece |
Quick Reference: Setup Order
1. Pair Slack workspace
└── Install app → Get code → Paste in console
2. Give access
└── Create bundle → Add connections → Use dedicated accounts
3. Set spend limit
└── Required on Team plans, recommended on Enterprise
4. Test
└── Basic task → Per-connection task → Check audit logsQ&A
1. Who can set up Claude Tag?
You need Owner permissions in your Claude organization to pair a workspace and create Access bundles. Admins can view settings and add credentials to existing bundles, but can't complete the initial pairing.
2. Do I need a Slack admin too?
Yes. Running @Claude connect and installing the app usually both need Slack workspace admin approval.
3. What happens if I don't add any connections?
Claude still works for Slack-only tasks like summarizing threads or catching people up on a channel (see How Claude Tag Works for details). You only need connections when Claude needs to act outside Slack.
4. Can I add tools later?
Yes, anytime. New connections apply to new threads immediately, but won't retroactively apply to an open thread.
5. Why use multiple Access bundles instead of one big one?
It lets you grant access by capability instead of all-or-nothing. A finance channel might only need read access to your data warehouse, while an engineering channel needs GitHub write access too.
6. Should I use my own login as Claude's credential?
No. Always create a dedicated service account or seat for Claude in each tool. This keeps its actions auditable and revocable without affecting your own access.
7. What's the difference between channel usage and DM usage billing?
Channel work draws from your organization's shared usage balance. DMs bill to each person's individual claude.ai account instead.
8. What happens when the spend limit is reached?
Claude stops the task and tells the requester in the thread it couldn't finish. An admin can raise the limit to let it continue.
9. My Slack install says it's "out of date." What do I do?
A Slack admin needs to click the reinstall link in Claude's reply, approve the new permission Slack shows, then run @Claude connect again. Don't uninstall the app first.
10. How do I know testing actually worked?
Two checks: Claude posts a real summary for the basic test, and for connected tools, the action appears in that tool's own audit log under the service account you set up.
