| Surface | Who changes it | What it controls |
|---|---|---|
| Claude Tag admin page | An Owner in your Claude organization | Access, behavior, and restrictions for channels, per scope |
| Usage page | An admin | Spend limits and per-channel usage analytics |
| The Configure link in any Claude reply footer | Channel members, unless an admin restricts editing | One channel’s instructions |
| Connectors settings on your own claude.ai account | You | Which of your personal tools apply in DMs |
The Claude Tag admin page
Everything an Owner configures for channels lives atclaude.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 options come from the models your organization allows for Claude Code; see Choose the model for a scope.
- 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. See Restrict where Claude Tag operates.
Spend limits and usage
Spend limits and usage analytics live atclaude.ai/admin-settings/usage/claude-tag, a different page than the Claude Tag admin page. It holds the organization-wide spend limit, per-channel limits, and the per-channel spend breakdown. See Set a spend limit for funding the usage balance and what users see when a limit is reached.
The Configure page
Every Claude reply in Slack ends with a footer, and its Configure link opens a claude.ai page for that channel. Anyone in the channel who is also a member of your Claude organization can edit the Channel instructions field there, unless an admin has restricted editing to admins. The page also shows the channel’s Connections, which admins set, so members can see the list but not change it. The Configure page and the scope’s settings dialog in admin settings write the same instructions, so a change from either place is visible in the other. See Configure Claude for a channel.Personal connectors on claude.ai
Connectors you add to your own claude.ai account, under Settings > Connectors, apply only in DMs with Claude, because a DM runs on your own account. A channel uses only the connections an admin attached to it, and personal connectors never apply there. 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.Related resources
- Customize Claude Tag: the layers that shape Claude’s behavior in a channel and who sets each one
- How agent identity works: why channels and DMs use different access
- Set up Claude Tag: where each setting is first created during setup