> 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/features/access-reviews/scenarios/reviews-with-saved-queries.md).

# Access Reviews with Saved Queries

Create Access Reviews from Query Builder searches to leverage existing saved queries.

### Overview

You can quickly define the scope of a review by choosing a [Saved Query](/4yItIzMvkpAvMVFAamTf/features/search/saved-queries.md) when creating the configuration. Creating a review from a saved query enables you to create reviews on the results of saved queries featured in Veza [dashboards](/4yItIzMvkpAvMVFAamTf/features/insights/dashboards.md).

Many of Veza's out-of-the-box queries return a single entity type (unless **Show \[Destination Entities]** is enabled). Reviews using saved queries will show a single entity type or a relationship, depending on the chosen query.

{% hint style="info" %}
Some query settings are specific to the Configuration Query Builder, such as the option columns for an [intermediate role](/4yItIzMvkpAvMVFAamTf/features/access-reviews/configuration/presentation-options.md#show-intermediate-relationship). Other capabilities, such as the option to use [Saved Query Filters](/4yItIzMvkpAvMVFAamTf/features/search/filters.md#use-the-results-of-one-query-to-filter-another-query), are unique to the Access Visibility Query Builder.
{% endhint %}

{% hint style="info" %}
If you plan to [schedule reviews](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/schedule-access-review.md) for this configuration, the saved query must be **public**. The review scheduler runs in a system context and cannot access private queries. See [Query visibility](/4yItIzMvkpAvMVFAamTf/features/search/saved-queries.md#query-visibility) for more on public and private query settings.
{% endhint %}

### Access Reviews for Saved Queries

To create an access review Configuration with a Saved Query:

1. [Create a new Configuration](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/review-configuration.md).
2. In the configuration builder, click to open the **Saved Query** tab:
3. Choose from the list of **Saved Queries**.
4. Configure default reminders and Veza Actions.
5. **Save** the Configuration.

### See also

* [Query Builder](/4yItIzMvkpAvMVFAamTf/features/search/query-builder.md)
* [Saved Queries](/4yItIzMvkpAvMVFAamTf/features/search/saved-queries.md).


---

# 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/features/access-reviews/scenarios/reviews-with-saved-queries.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.