> ## 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.

# Apply settings to every repository

> Choose between Organization defaults, central configuration, workspace settings, global overrides, and a shared remote file, then set up the one that fits.

You can set review behavior once and apply it to every repository in your organization. Each approach below differs in whether repositories can change the values, whether the values live in Git, and which platforms support it.

## Before you start

* Decide whether teams may change the settings. If they must not, use [global overrides](https://docs.coderabbit.ai/configuration/guides/enforce.md).
* Know how [inheritance and merging](https://docs.coderabbit.ai/configuration/inheritance-and-merging.md) combine layers.

## Choose an approach

| | Organization defaults | Central configuration | Workspace settings | Global overrides | Shared remote file |
| - | - | - | - | - | - |
| Sets | Defaults | Defaults | Defaults | Enforced values | Defaults, per repository |
| Repositories can change them | Yes: a repository file or central file outranks them | Yes: a repository file outranks it | Yes | No: they win over every layer | Yes |
| Version-controlled | No, saved in the web interface | Yes, a file in the `coderabbit` repository | No | No | Yes |
| Where you set it | **Review settings** | Central `coderabbit` repository | Workspace management | **View mode** > **Global overrides** | `remote_config` in a repository file |
| Platforms | CodeRabbit Cloud | Every Git platform; self-hosted CodeRabbit too | SSO workspaces and linked self-hosted Git provider organizations on CodeRabbit Cloud | CodeRabbit Cloud | Repository form on every Git platform; URL form on any |

Use Organization defaults when admins manage the baseline in the web app. Use central configuration when the baseline should be reviewed and versioned like code, or when you're on self-hosted CodeRabbit. Use workspace settings when several organizations in one workspace share a baseline. Use global overrides only for the few values teams must not change. A shared remote file suits a group of repositories that shares one file without a central repository for the whole organization.

## Set Organization defaults

Organization defaults apply to every repository whose **Use organization settings** toggle is on, which is the default. A repository file or a central file takes priority over them.

1. Open **Review > Review settings**.
2. In **Select repositories**, select the **Organization defaults** row.
3. Change settings in the form, or set **View mode** to **YAML editor**.
4. Select **Apply changes**, then **Apply changes** again in the confirmation dialog.

See [Settings in the web app](https://docs.coderabbit.ai/configuration/web-app.md).

## Set up central configuration

1. Create a repository named `coderabbit` in your organization.
2. Add `.coderabbit.yaml` or `.coderabbit.config.ts` at its root.
3. Install CodeRabbit on the repository.
4. Open a pull request in a repository that has no file of its own and run [`@coderabbitai configuration`](https://docs.coderabbit.ai/configuration/guides/check-effective-configuration). Values from the file show `Central YAML`.

Central configuration applies to repositories without their own file. See [Central configuration](https://docs.coderabbit.ai/configuration/central.md) for how each Git platform finds the repository.

## Let repositories customize with inheritance

Add `inheritance: true` to a repository file so it keeps the central values it doesn't set. Without it, the repository's omitted keys resolve to schema defaults.

> [tab] Central file
>
> ```yaml .coderabbit.yaml in the coderabbit repository theme={null}
> reviews:
>   profile: chill
>   path_instructions:
>     - path: "tests/**"
>       instructions: "Check that tests cover the error path."
> ```

> [tab] Repository file
>
> ```yaml .coderabbit.yaml theme={null}
> inheritance: true
> reviews:
>   profile: assertive
>   path_instructions:
>     - path: "api/**"
>       instructions: "Check input validation on every endpoint."
> ```

> [tab] Result
>
> The repository uses the `assertive` profile and both path instructions: its own `api/**` entry first, then the central `tests/**` entry. A central entry with the same `path` as a repository entry is dropped.

## Use workspace settings

Enterprise customers with an SSO workspace can set a shared baseline for every organization in it. A workspace admin turns on **Use workspace settings as defaults** on **Workspace management > General**. Workspace settings then fill only the keys that no other layer sets. See [Workspace settings](https://docs.coderabbit.ai/configuration/workspace.md).

## Enforce values instead

Use [global overrides](https://docs.coderabbit.ai/configuration/guides/enforce.md) for values that no repository may change. Don't use them as general defaults.

## Share one file across repositories

A repository file that contains only `remote_config` is replaced by the file it points to. CodeRabbit follows the pointer once. Prefer central configuration for many repositories, and point `remote_config` at a repository rather than a URL, because repository sharing is more secure. See [Configuration file](https://docs.coderabbit.ai/configuration/file.md).

A TypeScript configuration can't use `remote_config`. It uses `includeRemote` to pull a shared fragment and combine it with its own settings in code. See [Share TypeScript fragments](https://docs.coderabbit.ai/configuration/central.md#share-typescript-fragments).

## Change many repositories in the web app

1. In **Select repositories**, check each repository, or **All**.
2. Select the **Edit** button below the list.
3. Change settings and apply them.

> [!WARNING]
>
> Saving in the multi-repository editor turns off **Use organization settings** in each repository that has changes. Every saved value, including fields you didn't edit, then replaces Organization defaults there. A repository file and global overrides still outrank them.

## Check the result

Open a pull request in a repository without its own file and post `@coderabbitai configuration`. Each value's `# Source:` comment names the layer that applies. See [Check which configuration a review used](https://docs.coderabbit.ai/configuration/guides/check-effective-configuration.md).

## What's next

> [card] [Enforce settings teams can't change](https://docs.coderabbit.ai/configuration/guides/enforce.md)
>
> Pin values with global overrides and lock the configuration branch.

> [card] [Inheritance and merging](https://docs.coderabbit.ai/configuration/inheritance-and-merging.md)
>
> See how CodeRabbit combines layers, lists, and nested values.

> [card] [Central configuration](https://docs.coderabbit.ai/configuration/central.md)
>
> Set up the `coderabbit` repository on your Git platform.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.