Skip to main content
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

​
Overview

1

Connect providers

Configure VCS and, if needed, PM in Connected Apps, Credentials, or Connectors.
2

Connect repositories

Go to Repositories, select the authorized repositories, and link credentials or installations.
3

Configure policy

Adjust language, review tiers, branch rules, blocked authors, and additional instructions.
4

Receive a PR/MR event

The provider sends an event to Acrity when a relevant change happens.
5

Run the review

Acrity evaluates the change according to the workspace and repository policies.
6

Publish and audit

The result appears in the Console and can be published to the code provider or PM tool.
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.

​
Settings that influence the review

​
Where to track

Track the review in the Ops dashboard. Use Audit Trail only for technical event details and diagnostics.

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