claude.ai/admin-settings/claude-tag and click Set up (or + Connect if a workspace is already paired). If you started setup earlier without finishing, you’ll be asked to Resume or Set up a new workspace. A four-step setup dialog opens:
- Set up Claude Tag for your workspace: install the Slack app and link it with a pairing code
- Give Claude Tag access: name an Access bundle and connect your most-used apps
- Set a spending limit: cap monthly spend
- Review and launch: turn on Claude Tag
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
| Prerequisite | Why you need it | If you don’t have it |
|---|---|---|
| Owner role in your Claude organization | Pairing a workspace and creating Access bundles are Owner-only writes; an Admin can view settings but not complete setup. | Ask an Owner to run setup, or have one promote you at claude.ai/admin-settings/members |
| A Slack workspace admin | Running @Claude connect requires a Slack workspace admin; installing the app usually does too (most workspaces require admin approval for new apps) | If that’s someone else, send them the install request now so the pairing code is ready before you pair your Slack workspace |
| Usage credits (Team plans) | Channel work draws from your organization’s usage balance; on a Team plan nothing runs until credits are loaded | Buy credits at claude.ai/admin-settings/usage |
| (Optional) A channel to test in | You’ll invite Claude to a channel to test that setup worked | Create a private Slack channel for the pilot, or pick any existing one |
Setup steps
All four steps run in one dialog. Each section below shows what you’ll see and what to do.Step 1: Set up Claude Tag for your workspace
A Slack workspace is your team’s space in Slack, at an address likeyour-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.
Step 1 shows three numbered substeps:
Install Claude for Slack
The Install Claude for Slack link opens the Slack Marketplace listing. Click Add to Slack there and approve the permissions.
Send `@Claude connect` in any channel
This message is shown with a copy button. In any channel of the workspace you just installed in, paste and send it. 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.@Claude connect fails, and pairing on Enterprise Grid.
Step 2: Give Claude Tag access
An Access bundle is a named set of credentials, repository grants, plugins, and instructions that Claude uses on behalf of anyone in the channels it covers.GitHub isn’t in this app list. It’s connected through the Claude GitHub App on a separate page after setup; see Configure GitHub access.
Step 3: Set a spending limit
Channel work draws from your organization’s usage balance, not from individual seats; the spend limit caps how much of that balance Claude in Slack can use each billing period. (DMs run on the user’s own claude.ai account and aren’t capped by this limit.)
If your organization has no usage credits, this step shows Buy usage credits instead with a Buy now button; load credits, then continue. Click Next.
See Set a spend limit for what counts toward the cap, per-channel limits, and what users see when it’s reached.
Step 4: Review and launch
Change a setting after setup
Everything you set during setup can be changed afterward on the Claude Tag admin page.| To change | Go to |
|---|---|
| Pair another workspace, or disconnect one | The Slack row’s ⋮ menu under Where Claude Tag works; see Manage workspaces |
| The Access bundle’s name, connections, repos, plugins, or instructions | Access bundles in the left navigation, or any scope’s panel on the Slack tab; see Give Claude access |
| The spending limit | claude.ai/admin-settings/usage/claude-in-slack; see Set a spend limit |
| Whether Claude Tag is enabled at all | The Enable Claude Tag for your organization toggle at the top of the 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.
See Test your setup for 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:| Guide | Do this when |
|---|---|
| Give Claude access | You skipped connections during setup, or a team needs another tool connected |
| Configure per-channel access | One channel needs more (or different) access than the default. Keep elevated credentials in private-channel scopes; the org baseline stays minimal. |
| Configure GitHub access | A team will hand Claude code work: branches, pull requests, CI |
| Restrict where Claude operates | Governance review: guest channels, member access, DM policy |
| Customize | Standing instructions, plugins, and what channel members can change |
| Pattern | What you do | What channel members experience |
|---|---|---|
| Pilot first | One bundle on one workspace or channel; widen after validating | Claude appears in a few channels first, with capability growing as scopes are attached |
| Single bundle everywhere | One broad bundle at organization defaults | Every channel gets the same capability on day one. Fits orgs that already grant tools broadly. |
Common setup issues
| You expected | But got | Do this |
|---|---|---|
A pairing code from @Claude connect | “Only Slack workspace admins can link…” | The person who sent @Claude connect isn’t a Slack workspace admin. Send the request to someone who is. |
| A pairing code | “…installation is out of date” | In Slack, go to Slack admin → Manage apps → Claude and approve the updated permissions, then send @Claude connect again. |
| The Slack row under Where Claude Tag works to show your workspace as connected | It still shows Not connected | The code may have expired (codes last 15 minutes) or come from a different workspace. Send @Claude connect again for a fresh code. |
| A connected tool to work in your test | “I can’t reach…” | Connections only apply to new threads. Start a fresh thread before anything else. |
| The Where Claude Tag works section with a + Connect button | Only the legacy Claude in Slack toggles | Your organization isn’t enabled for Claude Tag. Contact your account team. |
Related resources
- Network requirements: what to allowlist before you start