Connections and scopes

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

​

Configure Slack scopes

Open Slack → Scopes in the CodeRabbit web app to manage the Slack Base Scope and named Slack scopes. The Base Scope controls the repositories and connections available to the agent by default. Named scopes refine that access for the Slack contexts offered by your workspace configuration. Depending on the options shown, an administrator may be able to target channels, conversations, users, user groups, repositories, or connections. To configure Slack scopes:

1. Confirm that CodeRabbit Agent for Slack is installed and connected to the intended Slack workspace.
2. Open Slack → Scopes.
3. Create or edit the Base Scope and select the default repositories and connections.
4. Create a named scope for a Slack context that needs different access.
5. Select from the targeting options offered for your workspace.
6. Choose the repositories and connections that CodeRabbit may use in that scope.
7. Save the scope and test the agent in a matching Slack conversation.

Base Scope setup can remain pending during installation, but CodeRabbit Agent cannot run in Slack until the Slack Base Scope exists. When you create it, all available connections are selected initially; deselect any that should not be available by default before saving.

​

GitLab repository access

For providers with per-repository selection, a named scope inherits the Base Scope repositories and adds any extra repositories selected in that scope. For GitLab, the selected token defines the effective repository set instead. A named Slack scope starts with the Base Scope GitLab token and the same GitLab access. Selecting a different GitLab token for the named scope replaces the inherited GitLab access; the two repository sets are not combined. Creating or updating a GitLab scope requires complete discovery of the catalog visible to the selected token. Saving fails if CodeRabbit cannot resolve exactly one usable GitLab credential or cannot discover the complete token-visible catalog. Verify that one valid GitLab token is selected and that CodeRabbit can retrieve the complete catalog, then save again. 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

Workspace administrators with workspace-management access can create and edit scopes, including the Base Scope. Slack Scope admins can manage their assigned named scopes, but they cannot edit 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 Slack Base Scope controls the default connections available to the agent. A named scope can inherit the Base Scope’s selection, prevent a connector from being used, or select a different saved connection when those choices are offered. Disabling a connection in a Slack scope affects only that scope. It does not disconnect or delete the saved connection, and it does not change Review scopes or Discord scopes.

​

Spend controls

CodeRabbit Agent usage is measured in agent minutes. Each scope can set two independent spend limits for its billing period: A named scope can override the user spend limit, the automation spend limit, or both independently. Free trials use the included Agent Minutes grant instead of scope spend limits, so trial access pauses only when the included minutes are exhausted or the trial expires.

​

What’s next