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

# Review flow

> From connected repository to review result in the Ops dashboard and code provider.

The Acrity review flow starts when a workspace connects a repository and ends with an auditable decision in the Ops dashboard and, when configured, in the code provider or PM tool.

## Review flow at a glance

```mermaid theme={null}
flowchart TD
    A["PR/MR event"] --> B["Inbound VCS webhook"]
    B --> C["Intake"]
    C --> D{"Policy gate"}
    D -->|"Branch rule or blocked author"| S["Skipped, no review"]
    D -->|"Eligible"| E{"Review tier"}
    E -->|"Fast"| F["Review run"]
    E -->|"Deep"| F
    F --> G["Publish to VCS checks and comments, and PM tool"]
    G --> H["Track in the Ops dashboard"]
    C -.-> T["Audit Trail (diagnostics)"]
    D -.-> T
    F -.-> T
    G -.-> T
```

## Overview

<Steps>
  <Step title="Connect providers">
    Configure VCS and, if needed, PM in `Connected Apps`, `Credentials`, or `Connectors`.
  </Step>

  <Step title="Connect repositories">
    Go to `Repositories`, select the authorized repositories, and link credentials or installations.
  </Step>

  <Step title="Configure policy">
    Adjust language, review tiers, branch rules, blocked authors, and additional instructions.
  </Step>

  <Step title="Receive a PR/MR event">
    The provider sends an event to Acrity when a relevant change happens.
  </Step>

  <Step title="Run the review">
    Acrity evaluates the change according to the workspace and repository policies.
  </Step>

  <Step title="Publish and audit">
    The result appears in the Console and can be published to the code provider or PM tool.
  </Step>
</Steps>

<Note>
  Repositories, Policy Engine, Credentials, Connectors, Webhooks, API Keys, and Audit Trail require a Workspace admin. Platform admins also have access. These roles are fixed capability sets defined by Acrity.
</Note>

## Settings that influence the review

| Setting                   | Location                | Effect                                                                                    |
| ------------------------- | ----------------------- | ----------------------------------------------------------------------------------------- |
| Workspace language        | `Workspace Settings`    | defines the default language for responses and comments; can be overridden per repository |
| Global review policy      | `Policy Engine`         | applies workspace-level tiers and default instructions                                    |
| Repository-level settings | `Repositories` > detail | overrides parts of the policy for one repository                                          |
| Branch rules              | repository detail       | avoids reviews in flows that do not need analysis                                         |
| Blocked authors           | `Policy Engine`         | ignores authors that should not generate reviews                                          |
| Allowed bots              | `Policy Engine`         | allows review of specific automations when desired                                        |
| Integrated PM             | repository detail       | enables task association and context publishing in the work management system             |

## Where to track

Track the review in the [Ops dashboard](/en/guides/ops-dashboard). Use Audit Trail only for technical event details and diagnostics.

| Screen            | What to check                                                  |
| ----------------- | -------------------------------------------------------------- |
| Ops dashboard     | review status, decision, findings, and operational follow-up   |
| `Overview`        | overall workspace health                                       |
| `Repositories`    | readiness, credentials, webhooks, last review, and alerts      |
| repository detail | settings, PM, review, bootstrap, and security scans            |
| `Audit Trail`     | technical event details, diagnostics, and administrative audit |
| code provider     | checks, comments, and statuses published by Acrity             |

## Pause or resume reviews

In the repository detail page, a Workspace admin can pause reviews for maintenance, migration, or investigation. While paused, new changes do not follow the normal review flow. Resume when credentials, webhooks, and policies have been validated.

## Best practices

* Start with a few critical repositories and validate behavior before expanding.
* Document exceptions in the repository itself when they are specific to that codebase.
* Use branch rules to avoid reviews on mechanical merges or sync branches.
* Configure language and PM before first use in large teams.
* Use `Audit Trail` only when you need technical event details, diagnostics, or administrative audit context.