How to Set Up Claude Tag in Slack (and What to Lock Down First)

This is part of our Claude Tag field guide for agencies. Start with the overview: Claude Tag: A Builder’s Guide for Agencies.

Setting up Claude Tag in Slack takes a few minutes. The clicks are easy. The decisions you make while you click — who can reach it, which channels it sees, whether it’s proactive — are the part that actually matters. This is a security-first walkthrough: how to install it, and what to lock down before you do.

The install, in plain steps

1. Open the Install Claude for Slack link, which takes you to the Slack Marketplace listing.

2. Click Add to Slack and approve the requested permissions.

3. Choose the scope: the whole workspace (Anthropic’s recommended default) or a specific set of channels.

One important gotcha: only a Slack Primary Owner or Owner can set up Claude Tag’s access and channels. The Admin role can’t do this part. If you’re rolling it out for a team, make sure an Owner is the one configuring access — otherwise you’ll get halfway and stall.

Lock this down first: who can reach Claude

Claude Tag gives you three Member Access modes. Pick the tightest one that still lets the right people work:

• Anyone in the Slack workspace — broadest; fine for a single internal team, risky if outside collaborators or clients are guests in your workspace.

• Any member of your Claude organization — narrower; ties access to your Claude org, not just Slack presence.

• Role-based access — tightest; only members whose role allows it. This one is available on the Claude Enterprise plan.

Default to the narrowest mode that doesn’t block real work. You can always widen later; clawing access back after the fact is harder.

Then decide what Claude can see

Access is who can talk to Claude. Visibility is what Claude can read — and it’s the bigger lever. Two settings deserve a deliberate decision, not a default:

• Cross-channel learning is permission-gated — Claude only learns from other channels and data sources you allow, and it doesn’t report from private channels. Grant it per channel, and never let a channel holding one client’s (or one regulated dataset’s) data feed learning that other work can draw on.

• Ambient mode turns Claude proactive. Leave it off for anything client-facing or sensitive, and on only where all the data is yours. We break down that call in Claude Tag Ambient Mode: Useful Teammate or Context-Bleed Risk?

The lock-down-first checklist

1. Map channels to trust boundaries before you enable anything — mark each channel internal, client, or regulated.

2. Set Member Access to the narrowest mode that works.

3. Ambient mode OFF by default; on only for internal-only channels.

4. Cross-channel learning granted per channel, never from client/regulated channels.

5. Isolate client work in its own space, not just a channel in one shared brain — the reasoning is in The Multi-Client Isolation Trap.

6. Keep a human on the ship button for anything that leaves the building.

If you’re migrating from the old app

Claude Tag replaces the legacy Claude in Slack app. The old app switches over on August 3, 2026, and administrators have a 30-day window to opt in and control channel-level access. Don’t treat the migration as a silent upgrade — it’s the moment to redo these access and visibility decisions from scratch. More on what changed: Claude Tag vs. the Old Claude in Slack App.

For the exact, current setup screens, Anthropic keeps an admin setup guide in its documentation; the decisions above are what to bring to it. For the full field guide, start at the pillar: Claude Tag: A Builder’s Guide for Agencies.