> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coderabbit.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Review scopes

> Control which saved connections CodeRabbit can use when reviewing pull requests in specific repositories.

Review scopes control the [connections](/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.

<Steps>
  <Step title="Open Review scopes">
    Select the organization you want to configure, then open [Review → Scopes](https://app.coderabbit.ai/review/scopes) in the CodeRabbit web app.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Choose default connections">
    Review the selected connections and deselect any that reviews should not use by default, then save the Base Scope.
  </Step>
</Steps>

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

<Steps>
  <Step title="Open Review scopes">
    Go to [Review → Scopes](https://app.coderabbit.ai/review/scopes) and select the action to create a named scope.
  </Step>

  <Step title="Describe the scope">
    Enter a clear name and description so other administrators understand which repositories and access policy the scope represents.
  </Step>

  <Step title="Assign repositories">
    Select the repositories that should use this scope. A repository can belong to only one named Review scope.
  </Step>

  <Step title="Choose connection behavior">
    For each connector, inherit the Base Scope selection, prevent the connector from being used, or choose a specific saved connection.
  </Step>

  <Step title="Save the scope">
    Review the repository assignments and connection choices, then save.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## Connection choices

| Choice                        | Use it when                                                                               |
| ----------------------------- | ----------------------------------------------------------------------------------------- |
| **Inherit from Base Scope**   | The repository should use whichever connection the Base Scope selects for this connector. |
| **Don’t use this connection** | The repository must not use this connector, even though the Base Scope allows it.         |
| Specific connection           | The repository should use a different saved account or server than the Base Scope.        |

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](/connections/scopes#scope-resolution-examples).

## What's next

<CardGroup cols={1}>
  <Card title="Scopes overview" href="/connections/scopes" icon="shield" horizontal>
    Review Base Scope behavior, connection choices, examples, and troubleshooting.
  </Card>

  <Card title="Connections" href="/connections" icon="plug" horizontal>
    Add and name the direct or MCP connections available to Review scopes.
  </Card>
</CardGroup>