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

# Settings in the web app

> Edit organization defaults and repository settings in the CodeRabbit web interface, choose which saved settings a repository uses, and save your changes.

The web interface at app.coderabbit.ai is where you edit settings without a configuration file. You can set **Organization defaults** for every repository, or **Repository settings** for one repository or several. A `.coderabbit.yaml` file in a repository or in your [central configuration](https://docs.coderabbit.ai/configuration/central.md) overrides both.

## Open the settings editor

**1. Open Review settings**

Go to app.coderabbit.ai and select **Review > Review settings** in the sidebar.

**2. Pick what to edit**

**Select repositories** lists your repositories with an **Organization defaults** entry above the repository search. Select a repository name, or select **Organization defaults**.

**3. Come back later**

The button at the top of the settings index shows your current selection. Select it to return to **Select repositories**.

You can also open a repository's settings from **Repositories** in the sidebar. Select the repository name, or the **Reviews** shortcut in its **Settings** column. With repositories checked in that list, **Review settings** opens the editor with them selected.

## Find a setting

With one repository or **Organization defaults** selected and **View mode** set to **All Settings**, the settings index on the left groups the settings into **General**, **Reviews**, **Chat** and **Knowledge base**. **Reviews** expands into pages such as **General**, **Auto review** and **Tools**.

**View mode** above the form chooses what the page shows.

| View mode | Shows |
| - | - |
| **Concise** (default) | The most commonly used settings |
| **All Settings** | Every available setting |
| **YAML editor** | The settings as YAML. See [Edit settings as YAML](#edit-settings-as-yaml). |
| **Global overrides** | YAML that CodeRabbit applies on top of every other layer. Offered for organization defaults and workspace settings, not for repositories. See [Global overrides](https://docs.coderabbit.ai/configuration/global-overrides.md). |

To search, press Cmd+K on Mac or Ctrl+K on Windows and Linux, or select **Search** in the sidebar. Each result shows the section that contains it, for example **Reviews > Auto review**.

## Edit organization defaults

Organization defaults set the configuration for every repository in the organization that uses them. By default, every repository does.

1. Select **Organization defaults** above the repository search. This clears any repository selection. You can't combine it with a multi-repository edit.
2. Change settings in the form, or switch **View mode** to **YAML editor**.
3. Select **Apply changes**, then **Apply changes** again in the confirmation dialog.

On Azure DevOps Server and Harness, the sidebar also has an **Organization settings** item that opens the same screen.

The **Global overrides** view mode opens the editor for YAML that CodeRabbit applies on top of every other layer. See [Global overrides](https://docs.coderabbit.ai/configuration/global-overrides.md).

## Edit a repository's settings

Select a repository name to open its settings. Selecting a name adds it to any repositories you already checked, so clear the other checkboxes first if you want to edit one repository.

A repository's saved settings apply only while **Use organization settings** is off on the repository's **General** page.

## Choose which web settings a repository uses

For a selected repository, the **Use organization settings** toggle on the **General** page chooses which saved web settings apply.

| Use organization settings | Saved repository values used? | Other settings editable? |
| - | - | - |
| On | No. The organization defaults apply. | No |
| Off | Yes | Yes |

> [!WARNING]
>
> Turning **Use organization settings** off doesn't copy the organization defaults into the repository's saved settings. Values such as automatic reviews can differ from what the organization had. Check them in **Review changes** before you submit.

A change to the toggle takes effect only after you apply and submit it. A configuration file in the repository or in the `coderabbit` repository overrides both choices. In the output of `@coderabbitai configuration`, these layers appear as `Repository UI` and `Organization UI`. The **About configuration sources** button, an info icon in the page header, summarizes these rules.

## Edit several repositories at once

**1. Check the repositories**

In **Select repositories**, check two or more repositories, or check the box that selects every repository on the page. The editor beside the list then edits all checked repositories.

**2. Edit the settings**

Change the settings you want to apply to every checked repository.

**3. Apply**

Select **Apply changes**. If you changed a list setting, the **Review list changes** dialog shows each repository's result first. Select **Confirm changes** to save.

Text, number and on/off settings overwrite only the fields you edit. Mixed values stay unchanged until you edit them. List settings have three modes.

| List mode | Effect |
| - | - |
| **Add rules** / **Add items** (default) | Appends new entries and skips identical ones. Existing path instructions keep their instructions. |
| **Update matching paths** | Path instructions only. Updates rules with exactly the same path. |
| **Replace all** | Replaces the list. An empty list clears it. |

> [!WARNING]
>
> Saving turns **Use organization settings** off for every changed repository. All of its saved values, including fields you didn't edit, then replace the organization defaults. Repository files and global overrides still outrank them.

## Edit settings as YAML

The **YAML editor** view mode opens a YAML editor with syntax highlighting and schema validation. It shows only values that differ from the defaults, in the same format as a configuration file, so you can move settings between the web interface and a repository. Switch **View mode** back to **Concise** or **All Settings** to return to the form. You can't save while validation errors remain.

> [tab] YAML V2
>
> ```yaml theme={null}
> reviews:
>   profile: assertive
> ```

> [tab] YAML V3
>
> Early Access (This feature is in early access. Enable it by setting `early_access: true` in your `.coderabbit.yaml`, or by toggling Early Access on the web interface.)
>
> V3 is a limited preview. Adding `version: 3` doesn't give your organization access.
>
> Organizations in the preview get a V3 editor instead. A **Settings** and **YAML** toggle switches between the form and the review policy YAML, and the form has the sections **General**, **Review behavior**, **Automatic reviews**, **Review output**, **Tools** and **Fun**. **Apply changes** asks for confirmation before it saves. The V3 editor edits one repository or the organization defaults at a time.
>
> Settings that V3 YAML doesn't hold, such as the Knowledge Base and chat integrations, are on a repository's **V3 preferences** page in the settings index, for repositories in the preview. See [Migrate configuration to V3](https://docs.coderabbit.ai/configuration/guides/migrate-to-v3.md).

## Preview review output

The **Preview** panel beside the form shows mock pull request output built from your current settings:

* The summary in the pull request description.
* The review comment: findings, prompts for AI agents, and the walkthrough with its changes table, sequence diagram, review effort estimate, related issues and pull requests, and suggested labels and reviewers.
* Merge risk, pre-merge check results, finishing touches, review info, review details and the poem.
* Inline finding threads.

Show or hide the panel with **Preview** next to **Apply changes**. It isn't shown in the YAML editor or global overrides. Settings that affect output have a **View** button that opens the panel at the affected section.

> [!NOTE]
>
> **Preview** illustrates output sections. It isn't the configuration a repository uses. To see what a real review used, post `@coderabbitai configuration` on a pull request. See [Check which configuration a review used](https://docs.coderabbit.ai/configuration/guides/check-effective-configuration.md).

## Save and review changes

The save flow depends on the editor.

| Editor | Steps |
| - | - |
| Organization defaults | **Apply changes**, then **Apply changes** in the dialog |
| Repository settings | **Apply changes**, then **Submit changes** in the **Review changes** dialog |
| Global overrides | **Apply changes**, then **Apply changes** in the dialog |
| Several repositories | **Apply changes**. After a list change, **Confirm changes** in the dialog |

On GitHub Cloud, **Review changes** also shows the configuration a repository uses before and after your change.

A form save stores every value, including untouched defaults. A **YAML editor** save stores only values that differ from the defaults. Dense values outrank inherited ones, which matters for [workspace settings](https://docs.coderabbit.ai/configuration/workspace.md) and [inheritance](https://docs.coderabbit.ai/configuration/inheritance-and-merging.md).

## What's next

> [card] [Resolution order](https://docs.coderabbit.ai/configuration/resolution.md)
>
> See how CodeRabbit combines web settings with files.

> [card] [Check the configuration used](https://docs.coderabbit.ai/configuration/guides/check-effective-configuration.md)
>
> Confirm what a review used.

> [card] [Apply to every repository](https://docs.coderabbit.ai/configuration/guides/all-repositories.md)
>
> Roll one setting out across the organization.


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