> ## 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 Dashboard > Triage repository attention, read fix rates and unresolved findings, and open the changes that need your next action. The Review dashboard shows what needs attention across your workspace's repositories. Start here to choose the next change to review or finding to fix. ## Prerequisites * [Review connected](https://docs.cloudthinker.io/guide/code-review/setup.md) to at least one repository. * Review view permission in the workspace. Ask a workspace Admin to check your role if Review is unavailable. * Completed reviews for finding statistics and recent fix rates. A new workspace can show empty cards until reviews finish. ## Triage what needs attention **1. Open Review** Click **Review** in the left navigation, then open **Overview**. The page header reads **What needs attention across your repositories**. **2. Choose the next action** Use the attention counts to open the matching list. | Count | What it points to | | - | - | | **Needs review** | Open changes with a review queued or running, including re-reviews | | **Changes requested** | Changes with blocking findings to fix | | **Open findings** | Unresolved findings on active changes | | **Pipelines to analyze** | Failed pipeline runs awaiting analysis | These counts describe different kinds of work. Do not add them together as a count of unique changes. **3. Work the change** Open a change from the resulting list. Read its verdict and findings, then decide what to fix or investigate. See the [Review workspace](https://docs.cloudthinker.io/guide/code-review/review-workspace.md) for finding actions, re-reviews, and merging. For failed CI runs, follow [Pipelines](https://docs.cloudthinker.io/guide/code-review/pipelines.md). **Success state:** you have opened the specific change or pipeline behind a dashboard count and know its next action. ## Read the recent fix rate **Recent fix rate** shows the share of findings fixed before merge. The card combines this week's percentage with a weekly chart. * Read **fixed pre-merge** below the headline percentage. * Hover over a weekly bar to see the percentage and the number fixed out of the total. * Read **pts vs last week** as percentage points, rather than a percentage increase. For example, a move from 40% to 50% is an increase of 10 percentage points. The rate counts findings, not changes. A change with several findings contributes several items to the rate. Each week groups findings by when they were raised. A fix counts toward the rate if it happened before or at merge, including fixes on changes still open. Fixes after merge remain in the total but do not raise the rate. Withdrawn findings and findings acknowledged without a fix are excluded. A dash means no headline rate is shown for the current period; earlier weeks can still have rates. **No fix rate yet** means none is available across the displayed weeks. Neither means every finding was left unresolved. ## Read the unresolved backlog **Unresolved backlog** counts unresolved findings across reviewed changes, including changes that already merged. Its severity breakdown helps you see the most urgent outstanding work. This scope is broader than the **Open findings** attention count, which covers active changes. Merging a change does not make an unresolved finding disappear from the backlog. Below the total, the card can show: | Signal | How to read it | | - | - | | **new last week** | Findings raised last week, rather than the total outstanding now | | Comparison with the previous week | Whether new findings increased or decreased | | Review count | How much review activity accompanied those findings | | **weeks falling** | Consecutive weeks with fewer new findings | Read the review count alongside the trend. Fewer new findings can accompany fewer reviews; the chart alone does not explain the cause. ## Open a recent review Use **Recent reviews** to return to a recently reviewed change. Select a row to open its details and check the latest findings. This card is a shortcut to individual reviews. Use the full **Reviews** page when you need list filters or older changes. ## Follow repository and learning context The **Codebase Atlas** section links reviewed work to its repository map. Open a repository to see where merged changes landed. When there are no maps or cited Learnings, the dashboard can show **Get more from Review** instead. Use **Turn on Codebase maps** or **Turn on Learnings** to get started. Follow [Codebase Atlas](https://docs.cloudthinker.io/guide/code-review/codebase-atlas.md) to build your first map. The **Learnings** section shows rules cited by reviews. Select a rule to inspect it, or click **All learnings** to open the full list. **No cited learnings yet** does not mean your saved Learnings were deleted. This dashboard section needs reviews that cite them. See [Learnings](https://docs.cloudthinker.io/guide/code-review/learnings.md) to manage the rules themselves. For developer comparisons, historical quality metrics, and repository PDFs, open [Review Insights](https://docs.cloudthinker.io/guide/code-review/analytics.md). ## Troubleshooting > [accordion] Could not load the Review overview > > Click **Retry**. If the error continues, ask an Admin to check your workspace access and Review connection. > [accordion] No reviewed changes yet > > Recent reviews appear after a connected repository receives a change and Review runs. Check repository setup and review filters if nothing arrives. > [accordion] Open findings and Unresolved backlog show different totals > > **Open findings** covers active changes. **Unresolved backlog** also includes merged changes. Compare their scopes before treating the difference as missing data. > [accordion] No unresolved findings > > The dashboard has no unresolved findings to show. To inspect completed reviews or resolved findings, open **Reviews**. > [accordion] No fix rate yet > > The dashboard needs review and finding data to calculate a rate. Check back after reviews finish, or inspect an individual review directly. ## Next steps > [card] [Review workspace](https://docs.cloudthinker.io/guide/code-review/review-workspace.md) > > Read a change, settle findings, and decide how to proceed. > [card] [Review Insights](https://docs.cloudthinker.io/guide/code-review/analytics.md) > > Explore quality trends, contribution, and repository reports. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.