Skip to main content
CodeRabbit manages connections to external services at the organization level. CodeRabbit Agent for Slack does not manage its own connections. Instead, scopes control which of those organization-wide connections, along with which repositories, the agent can use in a given conversation. Slack must be installed and connected before administrators can assign scopes. Availability also depends on the corresponding subscription and workspace-management access.

How scopes apply in Slack

Scopes are shared across CodeRabbit products. You create and edit them on the Scopes page of the CodeRabbit web app, and the same scope can serve reviews, automations, and Slack conversations. The Slack app assigns those scopes. In Slack → Channel mappings, each assignment maps a set of Slack conversations and members to one scope. Conversations and members that no assignment matches use the Slack default and its repositories and connections. For example, if an assignment covers only selected members of a channel, everyone else in that channel uses the Slack default. On the Scopes page, that scope is marked Default for Slack. Assignments have no priority order. If more than one assignment matches both the conversation and the member of a request, CodeRabbit blocks the request instead of choosing one. CodeRabbit Agent cannot run in Slack until your organization’s Base Scope exists. Installing CodeRabbit Agent for Slack creates the Base Scope if it’s missing.

Create or edit a scope

  1. Open Scopes from the sidebar of the CodeRabbit web app.
  2. On the Overview tab, select Create scope. To change an existing scope, select Edit on its row.
  3. Enter a Scope name and, optionally, a Description.
  4. Choose the repositories and connections that CodeRabbit may use in this scope.
  5. Save the scope.
Because scopes are shared, editing a scope changes it everywhere it’s used, including reviews and other Slack assignments.

Assign a scope to Slack conversations

  1. Confirm that CodeRabbit Agent for Slack is installed and connected to the intended Slack workspace.
  2. Open Slack → Channel mappings.
  3. Under Assignments, select Add assignment.
  4. Under Conversations, choose what the assignment covers: selected channels, all public or private channels, direct messages, or a combination of these.
  5. Under Members, choose Everyone, or select Selected members or groups and pick individual members or Slack groups.
  6. In Use scope, choose the scope that applies.
  7. Select Apply assignment, then select Test saved assignments or try the agent in a matching Slack conversation.

Repository access

The Base Scope doesn’t list repositories. Runs under it can use every repository available to CodeRabbit Agent through your Git provider. A named scope uses only the repositories selected in it. They aren’t combined with the Base Scope’s access. A scope used in Slack can also select Use all repositories.

GitLab repository access

For GitLab, the selected token defines the effective repository set. A named scope inherits the Base Scope’s GitLab connection unless it selects a different one. Selecting a different GitLab connection replaces the inherited GitLab access; the two repository sets are not combined. Repository access warnings about a credential and the CodeRabbit installation seeing different repository sets apply only to providers with per-repository selection: GitHub, Bitbucket Cloud, and Azure DevOps. They do not apply to GitLab, where the token defines the effective repository set.

Who can use and manage scopes

Organization admins create and edit scopes on the Scopes page, and manage assignments and spend limits in Slack → Channel mappings. Scope admins have read-only access to the named scopes assigned to them and can’t see the Base Scope. Billing-only administrators cannot manage scopes. Users who cannot manage scopes may still use CodeRabbit Agent in the scopes assigned to them. Their access is limited by the repositories, connections, and other context rules that the matching scope allows.

Connection behavior

The Base Scope controls the default connections available to the agent. A named scope inherits the Base Scope’s connections unless you override them, and the scope form marks those connections Inherited. For a service that uses one connection, such as an issue tracker, choose Inherit from Base Scope, a different saved connection, or Don’t use this connection to keep the service out of the scope. For MCP connections, clear the checkbox of an inherited connection to keep it out of the scope. Removing a connection from a scope does not disconnect or delete the saved connection. It applies everywhere that scope is used.

Spend controls

CodeRabbit Agent usage is measured in agent minutes. Spend limits belong to Slack assignments and the Slack default, not to scopes. In Slack → Channel mappings, select Edit limits on an assignment, or Edit default limits under When no assignment matches. Each assignment has two independent limits for its billing period: The Slack default starts with a baseline interactive limit and no automation limit. An assignment can override the interactive limit, the automation limit, or both independently. Free trials use the included Agent Minutes grant instead of assignment and Slack default spend limits, so trial access pauses only when the included minutes are exhausted or the trial expires.

What’s next

Scopes overview

Understand Base Scope behavior, named-scope overrides, and connection resolution examples.

Connections

Add, name, reconnect, and inspect the external services available to your organization.

Admin roles and security

Review the broader administration and security model for CodeRabbit Agent.