> 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/configuration/1-step-review.md).

# 1-Step Access Reviews

Configure a new access review using the quick builder.

**Early Access**: Please contact the Veza support team to enable this feature.

### Overview

1-step access reviews enable administrators to quickly create, delegate, and initiate access reviews, without first creating a reusable review configuration.

The 1-step review wizard provides a streamlined builder for defining the scope of the review based on:

* **Pre-defined scopes** for common scenarios and applications such as Okta, AWS, and Salesforce.
* A **saved query**, either built-in or constructed using the query builder.

### Creating a 1-step review

When 1-step reviews are enabled, administrators and operators can choose from two options when creating a review on the **Access Reviews** > **Reviews** page:

* **1-Step**: Create a review using the quick builder by giving it a name, defining the scope, and configuring optional settings such as reviewers and due date.
* **Use Configuration**: Open the full review builder to create a configuration, which can be used for recurring certification campaigns using the same scope. See [Access Reviews Query Builder](/4yItIzMvkpAvMVFAamTf/features/access-reviews/configuration/access-reviews-query-builder.md) for more information on the full query builder.

To create a review with the 1-step builder:

1. On the **Access Reviews** > **Reviews** page, click **Create Review** > **1-Step**.

   ![1-Step Access Reviews](https://1967633068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZDkWMxox3pekd0NsZJ%2Fuploads%2Fgit-blob-d8828cb8b2c7b96ba90c60b3be3f41c44ebd829e%2F1-step-review.png?alt=media)
2. Enter the required details:
   * **Review name**: This will be used to identify the review in Veza and reviewer notifications. Names should be unique to simplify tracking and reporting.
   * **Scope**: Choose an option to define the entities and relationships to review:
     * **Quick Builder**:
       * **Application**: Choose a provider from [Integrations](/4yItIzMvkpAvMVFAamTf/integrations/integrations.md) added to Veza.
       * **Review Type**: The type of entities and relationships to review: e.g., "Okta user AWS IAM group memberships"
       * **Narrow Scope**: Choose specific data sources Veza has discovered.
     * **Saved Query**: Choose from any out-of-the-box or user-defined query created using the [Query Builder](/4yItIzMvkpAvMVFAamTf/features/search/query-builder.md) or [Separation of Duties page](/4yItIzMvkpAvMVFAamTf/features/separation-of-duties/sod-queries.md).
   * **Due date**: Specify the Date (UTC) and Timezone when the review must be completed.
   * **Reviewers**: See [Assigning Reviewers](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/assign-reviewers.md) for more on assigning reviewers and auto-assignments.
     * **Assign Reviewers**: Assign default reviewers for all rows in the review.
     * **Auto-assign reviewers**: Assign row-level reviewers based on Veza metadata like managers or resource owners.
     * **Fallback reviewers**: Used when an auto-assignment is prevented or can't be found.
   * **Second-level Reviewers**: Require [multi-level approval](/4yItIzMvkpAvMVFAamTf/features/access-reviews/configuration/multi-level-approval.md), with the option to assign to first-level reviewer's managers.
   * **Access Intelligence**: Show [risk scores](/4yItIzMvkpAvMVFAamTf/features/insights/risks.md) and risk level for rows in the reviewer interface.
3. Select **Create Review** > **Save as draft** to save a draft and preview the results, **Create Review** > **Publish now** to make the results available to reviewers, or **Create Review** > **Publish later** to [schedule it](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/draft-review.md#schedule-a-draft-to-publish-later).

Notes:

* New reviews created using the 1-step builder have the "1-Step" review type.
* A review configuration is created in the background, which can be used to re-initiate reviews with that scope and provide historical decision data.
* 1-step access reviews use [Digest Notification Settings](/4yItIzMvkpAvMVFAamTf/features/access-reviews/configuration/email-notifications.md) to notify reviewers of assignments and deadlines, with the option to configure more granular notifications, reminders, and orchestration actions after review creation.


---

# 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/configuration/1-step-review.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.
