Skip to main content
Claude Tag’s settings live on claude.ai, split across a few pages that each own a different kind of setting. Which page you need depends on what you’re changing. The table maps each surface to what it controls. Channel memory and routines aren’t in the table because you change them by talking to Claude in the channel; see what anyone can change from the channel. Owners can review both, as each scope’s memory files and scheduled work, from the Audit page, labeled Activity in the console.

​
The Claude Tag admin page

Everything an Owner configures for channels lives at claude.ai/admin-settings/claude-tag. Settings there apply per scope (a channel, a workspace, or the whole organization). A scope without its own setting inherits from its parent, and a channel’s setting overrides its workspace’s, so two channels can run with different connections, models, and instructions. Most controls are Owner-only; the permissions table lists each action and who can take it.
  • Access bundles: the connections, domain entries, repository grants, and plugins Claude uses in the channels a bundle covers. See Give Claude access.
  • Custom instructions: standing guidance Claude reads in every session on a scope. See Add custom instructions.
  • Default model: the model new sessions in a scope start on. The picker shows the models your organization allows for Claude Code, leaving out any that Claude Tag doesn’t support, so it can be missing models you see in Claude Code itself. See Choose the model for a scope.
  • Auto mode allow rules: plain sentences that pre-approve actions Claude’s permission checker would otherwise flag or stop in a scope’s sessions. See Auto mode allow rules.
  • Workspace pairing and restrictions: which Slack workspaces are paired, whether DMs are allowed, guest-channel behavior, who can invoke Claude, and which generation of the app answers in each scope (on the Team plan, a single Enable Claude Tag switch replaces the per-scope setting). See Restrict where Claude Tag operates.
  • Channel name rules: channel-name patterns that keep Claude out of matching channels or join it automatically to new public ones. See Block or auto-join channels by name.

​
Spend limits and usage

Spend limits live at claude.ai/admin-settings/usage/claude-tag, a different page than the Claude Tag admin page. It holds the organization-wide spend limit, the default spend limit for channels, per-channel limits, and each channel’s spend against its limit. If your organization bills through a reseller, this page is not available. See Set a spend limit for funding the usage balance and what users see when a limit is reached. Usage covered by a promotional credit isn’t counted on the usage page and shows as $0.00 there. To see each channel’s list-price spend for the current month including covered usage, use the List price column of the Spend by channel table at claude.ai/analytics/claude-tag. Spend trends live at claude.ai/analytics/claude-tag, the Claude Tag section of the Analytics dashboard. It shows total and projected spend, spend by channel, and spend by kind of work for the period you pick, and anyone with permission to view the Analytics dashboard can open it. It has no controls; see Usage analytics.

​
The Configure page

Every Claude reply in a channel ends with a footer, and its Configure link opens a claude.ai page for that channel; replies in DMs have no Configure link. You can also send @Claude !configure in the channel, and Claude replies with a link to the same page. Anyone in the channel who is also a member of your Claude organization can edit the Channel instructions field on that page, unless an admin has restricted editing to admins. The page’s Respond automatically toggle controls whether Claude replies in the channel without an @-mention; see Turn automatic replies on or off. The page’s Tools and access tab shows the channel’s resolved connections and any allowed domains. Members can see those lists but not change them there. The same tab’s Plugins card lists the channel’s plugins, and members can add plugins there unless an admin has restricted editing to admins. A Routines tab lists the channel’s routines with each one’s schedule, status, and last run. The Configure page and the Custom instructions field on the scope’s panel in admin settings write the same instructions, so a change from either place is visible in the other. See Configure Claude for a channel. On the Enterprise plan, an Owner can name channel managers for a channel. For them, the same page adds editable cards: the channel’s default model on the General tab, and its repositories and access bundles on the Tools and access tab.

​
Personal connectors on claude.ai

Connectors you add to your own claude.ai account, under Customize > Connectors, apply in DMs with Claude, because a DM runs on your own account. A channel session uses the connections an admin attached to it. In organizations where personal connectors in channels is available, Claude can also use your personal connectors there for your own tasks, after you allow it. Slack has no connector settings of its own. See connectors on claude.ai for setting one up, and the troubleshooting entry if a connector you use on claude.ai is missing in Slack.

​
Claude Tag versus Claude Managed Agents

Claude Managed Agents is a separate product for developers, a pre-built agent harness that runs in managed infrastructure. You configure it on the Claude Platform through the Managed Agents API, and access requires a Claude API key. An agent there is defined by its model, system prompt, tools, MCP servers, and skills. Environments choose where its sessions run (a cloud sandbox, or a self-hosted sandbox on your own infrastructure), and scheduled deployments run it on a cron schedule. The two products don’t share settings. Nothing on the Claude Tag admin page configures a Managed Agent, and an agent defined on the Claude Platform doesn’t change how Claude behaves in Slack.