Skip to main content
Claude Tag is Claude working in your team’s Slack channels, with its own accounts in your tools. Open claude.ai/admin-settings/claude-tag. The page opens on setup until your first workspace is paired. It shows a step list, an FAQ, and a Start setup button (Resume setup if you started earlier without finishing). If you see View setup guide and Go to chat buttons instead, your signed-in account can’t run setup; start at Common setup issues. Setup walks you through each step: The rest of this page covers what to have ready before you start, each step in detail, and common setup issues.
If your team already uses the earlier Claude in Slack, the same steps apply and your existing app stays; see Migrate from the earlier app for what changes.

​
Before you start

If any of your services restrict traffic by IP, file the network requirements request with your network team early; in many organizations, IP allowlist changes take days to approve.

​
Setup steps

All steps run on one page. Everything you set is saved automatically, so you can leave and resume setup later. Each section below shows what you’ll see and what to do.

​
Pair your Slack workspace

A Slack workspace is your team’s space in Slack, at an address like your-team.slack.com; it contains all your channels. Pairing links one workspace to your Claude organization so @Claude can run in its channels and usage bills to your organization. This step shows four numbered substeps. The code is created in Slack and redeemed back on this setup page:
1

Add the Claude app to Slack

Click Add the Claude app to open the Slack Marketplace listing, then click Add to Slack there and approve the permissions.
2

Send `@Claude connect` as a new channel message

Copy the message shown and send it in any channel of the workspace you just installed in, as a new top-level message with no other text. A reply inside a thread is treated as a normal request and no code is issued. Claude replies with a pairing code valid for 15 minutes.Only a Slack workspace admin can run @Claude connect; anyone else gets a message naming who to ask. If that’s not you, send them the install request and have them return the code.
3

Paste the pairing code

Back on the setup page, paste the code into the input field (the placeholder reads workspace_…).
4

Choose where Claude runs

Under Choose where Claude can reply when tagged, select Entire workspace (recommended) or Specific channel (which asks for channel IDs).
Click Pair workspace. A confirmation screen shows the pairing worked; select Next: Choose Claude’s tools. See Pair your Slack workspace for the Slack-admin handoff template, what to do if @Claude connect fails, and pairing on Enterprise Grid.

​
Choose which tools to connect

Claude works in your tools with its own accounts, so everything it does is recorded under its own name. On this step you pick those tools; connecting them happens in a later step. GitHub is preselected and counts as one of your picks. The list suggests widely used tools; check the ones your team works in, or use Search all tools for a service that isn’t shown. Pick two more (three total, counting GitHub) to unlock Next; you can add more at any time. You can skip connecting the tools you pick and finish that after setup. Without any connected tools, Claude still works in Slack conversations and can use web search and a default set of network hosts; it can’t act in a tool until that tool is connected. See Give Claude access for which services to connect first, and the per-service connection guides for credential fields per tool.

​
Connect GitHub

GitHub is managed through the Claude GitHub App rather than a credential, so it has its own step. What the step shows depends on whether the app is already linked to your Claude organization.
  • Not linked yet: the step walks through installing the Claude GitHub App, with a message you can copy for the GitHub organization owner if that isn’t you.
  • Already linked: the step is titled Choose your GitHub repos and lists each installation, so you can grant every repository or only specific ones.
These grants apply to every channel Claude is in. You can add repositories to specific channels later, or skip this step and configure GitHub access after setup instead.

​
Create accounts for the tools you chose

Claude needs its own account in each tool you picked besides GitHub (covered by the app in the previous step), so you can always see what it did and limit what it reaches. How agent identity works explains this model.
1

Set up an email for Claude

Create an address like claude@yourcompany.com with your email provider. Some tools support service accounts (tool-managed identities that don’t need an email) instead.
2

Invite Claude to each tool

In each tool you picked, create an account for that address, the same way you would for a new team member.
3

Connect each tool with Claude's credentials

Each of the other tools you picked is listed (GitHub isn’t; the app covers it). Click Connect and enter the credential for the account you created (not your personal login).
To finish this step later, select Skip and confirm past the warning that Claude won’t be able to act in the unconnected tools. See Give Claude access for how to create the accounts and what access to give them.

​
Launch Claude Tag

Channel work draws from your organization’s usage balance, not from individual seats; the spend limit you set here caps how much of that balance Claude Tag can use each billing period. (DMs run on the user’s own claude.ai account and aren’t capped by this limit.)
1

Set monthly spend limits

Choose from $500, $1,000, $2,500 (the default), $5,000, Unlimited, or Custom (a US-dollar amount up to $1,000,000).
2

Let members know they can now tag Claude

Choose whether Claude sends a DM to everyone in your Slack workspace after launch.
3

Click Launch Claude

Claude Tag turns on, and a confirmation screen summarizes what’s connected. Claude is now reachable in the workspace you paired.
To leave setup without turning Claude Tag on, select Finish later; everything you’ve set is saved, and the admin page shows a resume card that brings you back to where you left off. If your organization buys usage credits by card in US dollars and has none loaded, a Buy usage credits step appears before launch instead of the spend limit picker; load credits, or select Skip to continue without. Invoiced organizations and those billing in other currencies get the spend limit picker regardless of balance. See Set a spend limit for what counts toward the cap, per-channel limits, and what users see when it’s reached.

​
Change a setting after setup

Everything you set during setup can be changed afterward on the Claude Tag admin page.

​
Test that setup worked

In Slack, in your pilot channel, run /invite @Claude and then @Claude summarize this channel. An is thinking… status under your message means the app is installed and listening. A reply means the workspace is paired and the channel is on the new version. This task doesn’t touch any connection, so it isolates pairing from credential issues. The See it work page has more prompts that run with no connections, and a per-connection test that proves each credential works.

​
After setup

After your test passes, these guides cover what’s not part of initial setup: There are two common ways to roll out from here:

​
Common setup issues