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

# Review Personalization

> Choose review summary sections, tone and language, then set workspace defaults or customize individual repositories.

Choose what Review writes in its summary and how its comments read. Set a workspace default, then give individual repositories their own settings when needed.

## Prerequisites

* [Review is set up](https://docs.cloudthinker.io/guide/code-review/setup.md) in your workspace.
* You're a workspace **Admin** to save changes. Developers and Viewers can inspect the settings. See [roles and permissions](https://docs.cloudthinker.io/guide/security/roles.md).
* If you can't open the editor, contact CloudThinker support.

## Choose where a change applies

Open **Review → Settings → Customizations**. Click **Edit** beside **Summary layout** or **Tone & language**; a read-only user sees **View**.

Each editor has its own **Workspace** and **Repository** choices. Layout and tone settings have separate overrides and locks.

| Choice or status | What it means |
| - | - |
| **Workspace** | The default for repositories without their own override |
| **Repository** | Select a repository to inspect or change its settings |
| **Inherits workspace settings.** | The repository follows the workspace default |
| **Overridden** | The repository has its own settings |
| **Locked** | The workspace settings apply to this repository |

Changing a workspace default leaves repository overrides in place. To make one repository follow the default again, select it and click **Reset to workspace**, then **Save changes**.

To apply one default everywhere, select **Workspace**, turn on **Lock for every repository**, and save. Existing overrides stay saved but do not apply while locked. Unlocking restores them.

## Change the summary layout

**1. Open the layout editor**

In **Review → Settings → Customizations**, click **Edit** beside **Summary layout**. Select **Workspace**, or choose **Repository** and pick a repository.

**2. Choose and order sections**

Turn optional sections on or off. Drag a section to reorder it, or open its actions menu (⋯) and choose **Move up** or **Move down**.

Inspect **Preview** as you edit. On a narrow screen, switch between **Sections** and **Preview** at the bottom.

**3. Save the layout**

Click **Save changes**. Review the affected repositories and section changes, then confirm **Save changes**. The first change from the classic layout shows **Switch layout?**.

**Success state:** the editor saves your layout. The next review uses it; comments already posted do not change.

| Section | Behavior |
| - | - |
| **Review Coverage** | Locked; leads the comment with the open findings, severity and location |
| **Architecture Diagram** | Locked; describes the change visually, but is skipped for documentation-only, configuration-only or dependency changes |
| **Recommendation** | Locked; gives the merge recommendation based on open findings |
| **Change Overview** | Optional summary of what changed and why it matters |
| **Related Issues** | Optional verified references to linked issues |
| **Related MR/PRs** | Optional references to related pull or merge requests |
| **Blast Radius** | Optional explanation of affected callers and downstream behavior |

Locked sections cannot be turned off. A layout holds at most 18 sections, with at most 13 enabled at once.

> [!NOTE]
>
> If your own workflow parses the summary comment, update that workflow before the next review uses a changed layout.

## Add a custom section

**1. Create the section**

In the layout editor, click **Create custom section → Create manually**. Enter a **Title** of up to 60 characters and an **Instruction** of up to 500 characters.

Describe the question the section should answer. For example, a **Rollback Plan** section could ask which steps restore the previous behavior.

**2. Place and save it**

Click **Create section**. The new section joins the end of your list; drag it where you want it. Click **Save changes** and confirm to save the layout.

**Success state:** the section appears in the saved layout for the selected scope.

To revise a custom section, open its actions menu and click **Edit**, then **Save section**. To remove it, choose **Delete**, then confirm **Remove section**. Save the layout afterward.

You can also choose **Create with CloudThinker** to open a chat with a prepared request. If the layout has unsaved edits, save them with **Save and continue** first.

## Set tone and language

**1. Open the writing settings**

In **Review → Settings → Customizations**, click **Edit** beside **Tone & language**. Choose **Workspace** or a **Repository**.

**2. Choose the wording**

Select a **Language**, then choose **Lean** or **Detailed** under **Tone**. Inspect **Preview**; on a narrow screen, switch between **Settings** and **Preview**.

**3. Save your choices**

Click **Save changes**. Use **Discard** if you want to abandon unsaved edits.

**Success state:** the saved tone and language appear when you reopen the editor.

| Tone | What changes |
| - | - |
| **Lean** | States the risk and fix in a few sentences; the default |
| **Detailed** | Explains the risk and reasoning behind each finding |

Tone changes wording, never the findings or their severity. The default language is **English (US)**.

Other choices are English (UK), Vietnamese, Japanese, Korean, Chinese (Simplified), Chinese (Traditional), Thai, Indonesian, German, French, Spanish and Portuguese (Brazil).

The preview stays in English even when you select another language. The **Recommendation** verdict also stays in English.

## Troubleshooting

> [accordion] I can't edit a repository's customization
>
> **Check:** look for **Locked**. The workspace default applies while **Lock for every repository** is on.
>
> **Fix:** ask a workspace Admin to change the workspace default or unlock it. If you see **View** instead of **Edit**, you need an Admin to save changes.

> [accordion] The existing summary did not change
>
> **Cause:** saving a layout does not rewrite comments already posted.
>
> **Check:** reopen the editor to confirm the saved scope. Inspect the summary after the next review runs.

> [accordion] I can't add another section
>
> **Check:** the editor shows the enabled section count. A comment carries at most 13 enabled sections, and a layout stores at most 18.
>
> **Fix:** turn off an optional section, or delete a custom section you no longer need, then add yours.

## Next steps

> [card] [Manage repositories](https://docs.cloudthinker.io/guide/code-review/repository-management.md)
>
> Choose which Review features run on each repository.

> [card] [Learnings](https://docs.cloudthinker.io/guide/code-review/learnings.md)
>
> Teach Review your team's standards and business rules.

> [card] [Review workspace](https://docs.cloudthinker.io/guide/code-review/review-workspace.md)
>
> Read findings, apply fixes and follow a review.

> [card] [Review setup](https://docs.cloudthinker.io/guide/code-review/setup.md)
>
> Choose review modes and filters for incoming changes.


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