Skip to main content
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. 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.
This page is about workspace settings on CodeRabbit Cloud. On self-hosted CodeRabbit, 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.
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.
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. 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.

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

Resolution order

See where workspace settings sit among the layers.

Global overrides

Enforce settings that teams can’t change.

Apply to every repository

Choose the right layer for an organization-wide setting.