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

# Workspace settings

> Set a shared baseline for every organization in an Enterprise workspace, and decide whether it replaces or fills in organization settings.

Enterprise Plan (This feature is available exclusively as part of the Enterprise plan. Please refer to our pricing page for more information about our plans and features.)

Workspace settings are a shared baseline for every organization in an Enterprise workspace. You edit them once, and organizations that belong to the workspace use them as their baseline or as a source of defaults. This page explains the two toggles that control that, because their names are close and their effects differ.

## What workspace settings are

Workspace settings sit just above the schema defaults in the [resolution order](https://docs.coderabbit.ai/configuration/resolution.md). They apply to SSO workspaces and to self-hosted Git provider organizations that are linked to a workspace. Workspace global overrides, which sit at the top of the order, are covered in [Global overrides](https://docs.coderabbit.ai/configuration/global-overrides.md).

> [!NOTE]
>
> This page is about workspace settings on CodeRabbit Cloud. On [self-hosted CodeRabbit](https://docs.coderabbit.ai/configuration/self-hosted.md), workspace settings, workspace global overrides and workspace defaults aren't consulted.

## Open workspace settings

The same page opens from two places, depending on how your organizations are connected.

> [tab] SSO workspace
>
> Select **CodeRabbit configuration** under **Workspace management**. Workspace administrators, and users with the Admin role in any organization in the workspace, can save it. A custom role isn't enough.

> [tab] Linked self-hosted Git organization
>
> Select **Workspace settings**. Viewing needs permission to view Organization Settings. Saving settings or global overrides needs permission to update Organization Settings.

To edit global overrides, set **View mode** to **Global overrides** on the same page.

## Replace organization settings with workspace settings

The **Use workspace settings** toggle belongs to one organization. Find it in the **General** section of **Organization defaults**. It appears only for organizations that belong to a workspace.

**1. Open Organization defaults**

Select **Review > Review settings**, then **Organization defaults**.

**2. Turn on Use workspace settings**

In **General**, turn on **Use workspace settings**. The organization sections become read-only.

**3. Apply the change**

Select **Apply changes**, then **Apply changes** again in the dialog.

While it is on, CodeRabbit ignores the organization's own saved settings and its own organization global overrides. The workspace settings stand in at the organization position. Where a workspace value doesn't exist, schema defaults apply. CodeRabbit makes the same substitution when an organization has no saved settings at all.

## Fill unset values with workspace defaults

The **Use workspace settings as defaults** toggle belongs to the workspace. Find it under **Workspace management > General**. It is off by default, and only workspace administrators can change it. It is available to SSO workspaces on CodeRabbit Cloud.

When it is on, workspace settings fill only the keys that are still empty after every other layer has been applied. Explicit values and global overrides keep their precedence. The fill works even when `inheritance` is off, and a blank `inheritance` value counts as `true`.

| Value in the resolved configuration | Result |
| - | - |
| Missing scalar or nested value | Filled from workspace settings |
| Empty array | Filled from the workspace array |
| Non-empty array | Unchanged. No workspace entries are added. |
| Explicit `false`, `0` or empty string | Unchanged |

Inheritance appends unique parent entries to arrays. Workspace defaults never do. A repository with a non-empty `path_instructions` gets none of the workspace's path instructions.

| | Use workspace settings | Use workspace settings as defaults |
| - | - | - |
| Set on | One organization | The workspace |
| Effect | Workspace settings replace the organization's settings | Workspace settings fill empty keys |
| Default | Off | Off |

## Keep workspace defaults from being masked

A form save stores a dense object: every value, including untouched defaults. Those stored values count as set, so they mask workspace defaults. A save from the **YAML editor** stores only values that differ from the defaults, so omitted keys can receive workspace defaults.

**1. Open the repository or Organization defaults**

Select the configuration in **Review > Review settings**.

**2. Re-save from the YAML editor**

Set **View mode** to **YAML editor**, remove keys you want the workspace to supply, and apply the change.

**3. Check the result**

Comment `@coderabbitai configuration` on a pull request. Values filled from the workspace show `# Source: workspace defaults`.

## What's next

> [card] [Resolution order](https://docs.coderabbit.ai/configuration/resolution.md)
>
> See where workspace settings sit among the layers.

> [card] [Global overrides](https://docs.coderabbit.ai/configuration/global-overrides.md)
>
> Enforce settings that teams can't change.

> [card] [Apply to every repository](https://docs.coderabbit.ai/configuration/guides/all-repositories.md)
>
> Choose the right layer for an organization-wide setting.


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