Skip to main content
Review scopes control the connections that CodeRabbit can use for pull request reviews. Configure default access in the Base Scope, then create named scopes for repositories that need different accounts or stricter access. Review scopes require an eligible Review plan and organization-administrator access. Billing-only administrators cannot manage them.

​
Configure the Base Scope

CodeRabbit cannot use saved connections in reviews until your organization creates the Review Base Scope. During setup, all available Review connections are selected initially so administrators can review and adjust the default selection before saving.
1

Open Review scopes

Select the organization you want to configure, then open Review → Scopes in the CodeRabbit web app.
2

Create or edit the Base Scope

Start the Base Scope setup. During initial setup, all available Review connections are selected by default to preserve existing behavior.
3

Choose default connections

Review the selected connections and deselect any that reviews should not use by default, then save the Base Scope.
The Base Scope applies to any repository that does not match a named Review scope. When you add a new connection, you can optionally add it to the Review Base Scope during connection setup.

​
Create a named Review scope

1

Open Review scopes

Go to Review → Scopes and select the action to create a named scope.
2

Describe the scope

Enter a clear name and description so other administrators understand which repositories and access policy the scope represents.
3

Assign repositories

Select the repositories that should use this scope. A repository can belong to only one named Review scope.
4

Choose connection behavior

For each connector, inherit the Base Scope selection, prevent the connector from being used, or choose a specific saved connection.
5

Save the scope

Review the repository assignments and connection choices, then save.
6

Test on a pull request

Open or update a pull request in an assigned repository and confirm that CodeRabbit can use the intended connections. Test both an inherited connection and any explicit override or exclusion that matters to the scope.

​
Connection choices

If no named Review scope matches a repository, the Base Scope applies. Removing a connection from a named scope does not delete the saved connection or change its use in other scopes.

​
Example

Suppose the Base Scope selects Company Notion and Company Linear. A Backend scope assigned to backend repositories can select Engineering Linear and choose Inherit from Base Scope for Notion. Reviews in those repositories use Engineering Linear and Company Notion, while other repositories continue using the Base Scope selections. For explicit exclusions and multiple-account examples, see Scopes overview.

​
What’s next

Scopes overview

Review Base Scope behavior, connection choices, examples, and troubleshooting.

Connections

Add and name the direct or MCP connections available to Review scopes.