Skip to main content
Scopes control which repositories, connections, and spend limits Slack Agent can use in each conversation. Every workspace has a Base Scope that applies everywhere by default. Scopes let you override or extend those defaults for specific channels or DMs.

​
Start with the Base Scope

The Base Scope is created during the Quickstart setup flow. It sets the default repositories, connections, and monthly spend limit per user. Scopes build on top of it by adding repositories, swapping connections, or setting tighter limits. If a conversation does not match any scope, the Base Scope governs it entirely.

​
One scope per conversation

For any given conversation, Slack Agent resolves:
  1. The Base Scope, which always applies
  2. At most one matching scope, when the current channel or DM pattern matches one
That means the Base Scope is the workspace-wide baseline and a scope is the targeted override or extension for that specific Slack surface.
If more than one scope matches the same conversation, Slack Agent treats the match as ambiguous and blocks the request rather than guessing. Ensure scope patterns do not overlap.

​
Scope types

Scope typeUse it forWhat it controls
Base ScopeWorkspace-wide defaultsDefault repositories, connections, and spend limit
ScopeTargeted access for specific channels or DM workflowsChannel- or DM-specific repositories, connections, and spend rules

​
Inheritance rules

Scopes build on top of the Base Scope.
BehaviorHow it works
RepositoriesA scope inherits the Base Scope repositories, then adds any extra repositories selected in that scope
Non-MCP connectionsA scope keeps the Base Scope service choice unless the same service is explicitly replaced. Only one connection per non-MCP service type is allowed per scope. Duplicates are blocked
MCP connectionsMCP connections are additive, so scope-level MCP access combines with Base Scope MCP access. Duplicate MCP server selections are also blocked
Spend limitA scope can inherit the Base Scope baseline or set a narrower or different policy
In practice, the effective repository set is usually the union of Base Scope repositories and scope repositories.

​
Spend controls

Spend controls are configured at the scope level.
Scope typeBlank value behaviorExplicit unlimited behavior
Base ScopeDefaults to a baseline when left blankSet No limit explicitly
ScopeInherits or remains unset when left blankSet No limit explicitly
Use scope spend limits when a team, channel, or workflow should be more tightly controlled than the workspace default.

​
Scope admins

Scopes can be managed by assigned scope admins, but the Base Scope remains reserved for global admins. That lets workspace admins delegate day-to-day scope tuning without giving every scope owner control over the entire Slack Agent workspace.

​
Roll out safely

For most teams, the safest rollout path is:
  1. Keep the Base Scope relatively conservative
  2. Add scopes only where a team needs different repositories, tools, or limits
  3. Expand gradually as usage patterns become clearer

​
What’s next

Connections

Learn how workspace-level connections are created once and then selected per scope.

Admin roles and security

See who can create scopes, who can edit them, and who can see activity across the workspace.

Working in Slack

Understand how the current scope changes what Slack Agent can do in a real conversation.