Claude Tag: Your New AI Employee in Slack
You will have Claude working in Slack in its two modes: as its own AI employee inside channels with a role and permissions for each channel, and as your personal assistant in DMs. You will also have a first use case picked to try.
Was Sie brauchen
A Slack workspace where you can add apps and change settings
A Claude account (claude.ai)
Optional: separate Gmail, Google Drive and Notion accounts to give Claude as its own
Schritt für Schritt
Connect Claude to your Slack workspace
Connect Claude to your Slack workspace (this is Claude Tag, Anthropic's Claude in Slack). This gives you two modes: Claude inside channels, where it acts as its own employee, and Claude in direct messages, where it works with your own information.
Give Claude its own accounts for channel work
In channels, Claude behaves like its own AI employee. Give it access to its own Gmail, Google Drive and Notion accounts instead of yours. In channels it acts more like an agent (similar to Claude Code and Claude Cowork) than an assistant.
Set a role and permissions for each channel
Decide what Claude does in each channel. For example, give it a legal role in your legal channel. Set what it can access per channel, and connect different accounts and tools depending on where it sits.
Change the guest setting if your channels have guests
If a channel includes guests (clients, contractors), Claude will not respond to them by default. Find that setting and change it yourself if you want guests to be able to ask Claude questions.
Use DMs for your own information
Send Claude a direct message in Slack. Here it uses your own connections, like Claude Cowork in the desktop app. Prompt it as usual and ask questions about your own information. Rule of thumb: its own employee lives in channels, your own information lives in DMs.
Schedule proactive tasks
Give Claude scheduled tasks so it works without being asked, for example a task that runs every Monday or every Tuesday.
Pick your first use case
Claude remembers everything inside a channel. Choose one to start: - Client account manager: add it to each client's channel so clients can ask it questions - Sales handoff: it retrieves what setters and closers said, even if nobody logged it in the CRM - Community listening: it reads a whole channel for reporting and a content pipeline
Bridge email, project tools and code
Ask Claude to check every day what was said in a channel and pass it on, which closes the gap between Slack, email and project tools like Trello or Notion. If you are a developer, ask it to fix bugs directly from Slack.
Prompt Claude together as a team
Claude works multiplayer in a channel. When one person sends a request and Claude starts working, a second person can jump in and add or correct a piece of information it missed.
Worauf Sie achten sollten
Claude does not answer guests in a channel until you change that setting yourself.
Channels and DMs use different connections: in channels Claude uses the accounts you gave it, in DMs it uses yours. Keep private information in DMs.
My warning: usage will probably get expensive over time. On Team billing you get $2,000 of usage, so use that window to test whether it fits your organization.
The use cases are ideas I found on X and had not set up myself yet, so start with one and test it before rolling it out.
