> For the complete documentation index, see [llms.txt](https://docs.veza.com/4yItIzMvkpAvMVFAamTf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veza.com/4yItIzMvkpAvMVFAamTf/product-updates/blog/access-reviewer-enhancements.md).

# UX Update - Enhanced Reviewer Experience for Veza Access Reviews

Learn more about the latest changes to improve the reviewer interface for Veza Access Reviews.

An updated reviewer UX is now available for all customers using Veza for Access Reviews. We’ve responded to your feedback and simplified the interface to save reviewer time and simplify decision-making when rejecting or approving rows.

#### Streamlined results view

To make it easier for reviewers to focus on actionable items, rows that aren’t assigned to the current reviewer are now hidden, along with rows that are signed off. You can now optionally show these relationships using the **Filters** menu:

![Use filters to show hidden rows.](https://1967633068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZDkWMxox3pekd0NsZJ%2Fuploads%2Fgit-blob-835861159fc89585558f616dd3c100fc047a50a9%2Faccess-reviewer-changes-1.png?alt=media)

Users with the Access Reviewer role can still only see rows they are assigned as a reviewer.

#### Simplified bulk actions

In the original design, reviewers could sign off on multiple rows using a **Smart Action**, which applied to all rows matching the filter criteria. We’ve removed this additional step, so reviewers can now approve, reject, add a note, or re-assign reviewers by applying a filter and selecting some or all rows to apply a change to:

![Apply bulk actions by selecting multiple rows and choosing an action from above the list of results.](https://1967633068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZDkWMxox3pekd0NsZJ%2Fuploads%2Fgit-blob-ec4a841b7e90f97767152b846e2a117f5c71dae6%2Faccess-reviewer-changes-2.png?alt=media)

#### Select all items

It is now possible for reviewers to select all items in a review - *even across multiple pages*. This is useful if users want to perform a bulk action on a large quantity of items across pages.

![Use the Select All Rows button to act on all results across all pages.](https://1967633068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZDkWMxox3pekd0NsZJ%2Fuploads%2Fgit-blob-05ea764583d9849ee4e7afd3b65430037c058025%2Faccess-reviewer-changes-3.png?alt=media)

#### Single-click approve and sign-off

Reviewers can now finalize decisions in bulk using the **Sign-off** button above the results, which can apply to all rows with decisions or the current selection. Reviewers no longer need to sign off on individual rows, saving time and reducing screen clutter.

![Finalize all or some results using the Sign-off button.](https://1967633068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZDkWMxox3pekd0NsZJ%2Fuploads%2Fgit-blob-0673c620e72e19b3f1bf9a036dc44a3f49f316fa%2Faccess-reviewer-changes-4.png?alt=media)

#### General improvements and simplified statistics

You can now quickly open the row details in a sidebar to inspect attributes and apply a decision using keyboard shortcuts:

![Click the details icon next to the selection checkbox to open the row in a sidebar.](https://1967633068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZDkWMxox3pekd0NsZJ%2Fuploads%2Fgit-blob-44b8f817e51a14bcc6c9d5565ba41e3eb41fb87b%2Faccess-reviewer-changes-5.png?alt=media)

Additionally, progress indicators and review details now take up less screen real estate. We've cleaned up the interface for a sleeker presentation overall, and improved responsiveness and consistency when selecting and acting on rows.


---

# 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.veza.com/4yItIzMvkpAvMVFAamTf/product-updates/blog/access-reviewer-enhancements.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.