> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/updates/release-notes/revamped-reviewer-experience.md).

# Revamped Reviewer Experience

The reviewer experience has been redesigned to give reviewers a clearer, more actionable view of their work. **My Tasks** is now a visual dashboard with workload summaries, progress metrics, and insights across assigned tasks, while the former **Priority Inbox** has been expanded into the **Campaign Reviewer Progress Dashboard** with dedicated views for understanding campaign progress, prioritizing work, and taking review actions.

### [**My Tasks**](/user-access-reviews/access-review-management/tracking-campaigns-and-performing-access-reviews/reviewer-experience.md#my-tasks)

The redesigned **My Tasks** page replaces the previous task list with a dashboard that gives reviewers an at-a-glance view of their workload and progress.

**What’s new:**

* **Visual workload overview:** Reviewers can now see task counts, completion progress, and other key metrics through interactive cards and charts instead of a simple list of assigned tasks.
* **Insights into assigned work:** The dashboard surfaces information across access reviews, comments, campaigns, and findings, helping reviewers quickly understand what requires their attention.
* **Compact grid view:** The new grid view replaces the previous full-width list layout, making better use of available space and allowing reviewers to see more tasks at a glance. Reviewers can also group tasks by **Status** or **Type** to organize their workload in the way that best fits their workflow.

### [**Campaign Reviewer Progress Dashboard**](/user-access-reviews/access-review-management/tracking-campaigns-and-performing-access-reviews/reviewer-experience.md#campaign-reviewer-progress-dashboard)

The former **Priority Inbox** has been expanded into the **Campaign Reviewer Progress Dashboard**, providing a more complete view of a reviewer's progress within a campaign.

**What’s new:**

* **Campaign Overview:** A new Overview tab provides campaign-level visibility through review status, identity status, key insights, top buckets, and other metrics. Interactive insights allow reviewers to drill down directly into the relevant reviews.
* **Priority Inbox:** The existing Priority Inbox experience is now a dedicated tab within the dashboard, organizing reviews into priority buckets so reviewers can focus on work that requires attention.
* **Reviews:** A new Reviews tab provides a centralized table of the campaign's reviews, where reviewers can view and action their assigned reviews.
* **Interactive drill-downs:** Reviewers can select insights from the Overview or buckets from the Priority Inbox to jump directly to the relevant reviews in the Reviews tab.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.balkan.id/updates/release-notes/revamped-reviewer-experience.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.