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

# Review settings

> Configure Propel review settings for code review and pull request summaries.

Use review settings to control how Propel runs across repositories.

## Available review settings

These setting areas are currently available for customer use:

| Setting area | What it does                                                    |
| ------------ | --------------------------------------------------------------- |
| Code Review  | Reviews pull requests and posts actionable comments.            |
| PR Summary   | Generates a summary so reviewers can understand changes faster. |

Some workspaces may also see UI testing settings when that feature is enabled.

## Configure review settings

1. Open **Review settings**.
2. Click **Configure** on the setting area you want to change.
3. Select the repository.
4. Update settings and save.

<Note>
  Workspace admins can configure company-level settings. Developers with linked VCS identity can configure personal review settings where available.
</Note>

## Code review settings

Common settings include:

* Review strictness and severity filtering.
* Comment detail level.
* Automatic approval policy.
* PR title update behavior.
* Branch targeting.

Use stricter settings for protected branches and broader settings for faster iteration branches.

## PR summary settings

You can tune summary detail level to match your review style:

* Concise
* Standard
* Detailed

Start with standard summaries, then adjust based on reviewer feedback.

## Rollout strategy

1. Start with one repository.
2. Validate review quality and summary usefulness for one week.
3. Expand to additional repositories.

## Next steps

1. Use [Logs](/features/logs) to inspect execution details.
2. Use [Insights](/features/insights) to track impact over time.
3. Add team guidance in [Knowledge base](/features/knowledge-base).