> ## 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.
# Where reviews appear
> Track review status, decisions, and findings in the Ops dashboard (Acrity Ops), and understand how it differs from the Audit Trail.
Reviews appear in the **Ops dashboard**, the companion app for review intelligence. It is where you follow what a review decided, which findings it raised, and how your reviews are trending across repositories. The Console configures reviews; the Ops dashboard is where you watch them happen.
## Open the Ops dashboard
The Ops dashboard is a separate app, **Acrity Ops**. Open it from the Console system switcher, the app menu labeled **Ops**. Selecting it takes you from the Console into Acrity Ops with the same workspace already in context.
## What it shows
The Ops dashboard is the live view of review activity for the selected workspace. In one place you can see:
Whether a review is in progress, finished, or needs attention.
The outcome each review reached, so you can act on it.
The issues a review raised, grouped so you can triage them.
The PR or MR each review is tied to, across your connected providers.
Who opened the change under review.
Summaries of how long reviews take and what they consume.
## Who can access it
The Ops dashboard is not limited to administrators. Members and above can open and view it, so the people who work with reviews day to day can follow status, decisions, and findings without administrative access.
| Role | Ops dashboard access |
| --------------- | ------------------------------------------------------------------------- |
| Workspace admin | Can view the Ops dashboard. |
| Maintainer | Can view the Ops dashboard. |
| Member | Can view the Ops dashboard. |
| Billing Manager | Focused on billing; the Ops dashboard is outside this role's usual scope. |
Roles are fixed capability sets defined by Acrity. They are not organization-configurable, so the same role grants the same access in every workspace. For the full description of each role, see [Roles and access](/en/get-started/roles-and-access).
## Ops dashboard vs. Audit Trail
The Ops dashboard and the [Audit Trail](/en/console/audit-trail) answer different questions. The Ops dashboard is live review tracking and intelligence: it tells you what reviews decided and what they found. The Audit Trail is the per-run execution log you use for diagnostics: it tells you whether a specific run completed, was skipped, errored, or is still running, and why.
| | Ops dashboard | Audit Trail |
| ------- | -------------------------------------------- | -------------------------------------------------- |
| Purpose | Live review tracking and intelligence | Per-run execution log for diagnostics |
| Answers | What did the review decide and find? | Did this run finish, and why did it fail or skip? |
| Access | Members and above | Workspace admin (platform admins also have access) |
| Where | Acrity Ops, from the Console system switcher | `Console > Audit Trail` |
Use the Ops dashboard to track and act on reviews. Switch to the Audit Trail when you need to diagnose a specific run.
```mermaid theme={null}
flowchart TD
A[PR or MR event] --> B[Review runs]
B --> C[Ops dashboard
status, decisions, findings]
B --> D[Audit Trail
per-run execution log]
```
## Where this fits
Configure reviews in the Console, then watch them in the Ops dashboard. If you are still setting up, start with the [Quickstart](/en/get-started/quickstart), then return here once your first PR or MR triggers a review. To see how a change moves from a connected repository to a tracked result, see [Review flow](/en/guides/review-flow).
Connect a repository and trigger your first review.
Follow a change from repository to tracked result.
Diagnose a specific review run.
See how the Console areas fit together.