Customize Claude Tag

Claude Tag is customized per channel and workspace (a scope), not per user. See what admins set in claude.ai, what anyone can change from the channel, and what stays fixed.

Claude Tag is in public beta. Features and behavior described here may change before general availability.

Claude Tag's behavior is shaped by four layers, each set in a different place:

Layer	What it is	Who sets it	Where
Connections	Credentials for the systems Claude can reach (GitHub, Drive, Datadog, your APIs)	Owner	Access bundles
Plugins and skills	Instructions that teach Claude how to use a tool or follow a process. A plugin bundles one or more skills.	Owner	Bundle Plugins tab or a skills repository
Custom instructions	Standing guidance read in every session at a scope (team conventions, output formats). Outranks channel memory.	Owner for any scope; channel members for the channel scope, from the Configure page	Per-scope instructions
Channel memory	Facts Claude saves while working in a channel	Anyone in the channel	By telling Claude

Connections and plugins decide what Claude can do; instructions and memory shape how it does it.

Settings admins control

Access and organization-wide behavior are set at claude.ai/admin-settings/claude-tag, per scope (a scope is a channel, a workspace, or your whole organization), so the same agent can work differently in different channels. Most controls below are Owner-only.

Setting	What it does	More
Custom instructions	Standing guidance read in every session on a scope, like team conventions. Outranks channel memory.	Add custom instructions
Plugins	Bundles of skills that teach Claude how to use a specific tool	Attach plugins
Connections	Which systems it can reach from each channel	Add connections
Claude in Slack version	Which generation answers (New, Legacy, or Off) in a scope	Migrate from the earlier Claude in Slack

Channel connections are separate from personal connectors

An Owner configures Claude's connections, plugins, and skills, and they apply per scope. They are separate from the connectors, skills, or MCP servers an individual user has set up in their own claude.ai or Claude Desktop account. A user's personal connectors are not available to Claude in a channel, and the channel's connections are not listed among that user's personal connectors in claude.ai.

To give Claude access to a tool that is not in the built-in connection list, including a custom MCP server, see add a custom connection.

Change behavior from the channel

Everything in the table below is open to channel members, with no admin involved.

To change	Say something like	More
How Claude formats output	"remember for this channel: post reports as a table"	Memory
How chatty Claude is	"ask before posting anything longer than a screen"	Memory
When Claude follows a thread	"stay quiet in this thread unless someone tags you"	Control when Claude Tag responds
What Claude does on a schedule	"every morning at 9, post a digest of open threads"	Set up routines
What Claude remembers	"what do you remember about this channel?" then correct it	Memory

Changes in the table above are saved to channel memory; verify one stuck by asking what it remembers.

Members can also tailor how Claude works in the channel from the Configure link in the footer of any Claude reply. The link opens a claude.ai page where anyone in the channel who is also a member of your Claude organization can edit settings for that channel, unless an admin has restricted editing to admins. The Channel instructions field on that page holds standing guidance that outranks memory. See configure Claude for a channel.

Settings no one can change

• The Claude app's name, @-handle, and avatar in Slack are the same in every workspace; there is no rename or rebrand setting.
• Channel sessions run on Claude Opus, with no setting to switch to Sonnet or Haiku. See current limits.

Related resources

• What Claude Tag remembers: how channel instructions are stored, shared, and corrected
• Good habits for working with Claude Tag: phrasings that make recurring output consistent
• How agent identity works: why access is set per channel