> 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/how-to/create-access-review.md). # Create a Review How to create a new one-time access review from a saved configuration. ### Overview Create a review to start a one-time review based on the specified configuration. In doing so, you can set the due date and assign default reviewers for all rows. You can also automatically apply decisions to some rows, or customize the time frame for which to review access. You can create a review as a draft, publish it right away, or schedule it to publish later. Select **Save as draft** to inspect the results and individually assign rows before triggering any email notifications specified in the review configuration. See [Draft Reviews](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/draft-review.md). Once the review is published, reviewers can log in to Veza to approve or reject access using the reviewer interface. ### Before you start You will need: * A saved review configuration. Review configurations define the scope of an access review. When [creating a configuration](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/review-configuration.md), owners can customize [Veza Actions](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications.md) and email notification settings that apply to all reviews for that configuration. * A user account with the Veza admin or operator [root team role](/4yItIzMvkpAvMVFAamTf/administration/administration/users/roles.md#root-team-access) is required to create configurations and start reviews. ### Create a new review 1. On the **Configurations** page, find the configuration you will create a review for. 2. Click the review name to open the **Details** page. 3. Click **Create Review** to open the review creation options. You now have two choices: * **1-Step**: Create a review and configuration simultaneously using the quick builder. See [1-Step Access Reviews](/4yItIzMvkpAvMVFAamTf/features/access-reviews/configuration/1-step-review.md) for detailed instructions. * **Use Configuration**: Create a review using a new or existing configuration to define the review scope(following the steps below). 4. If you chose **Use Configuration**, the review creation wizard will open with the following steps. 5. **Select Review Configuration**: * Leave this unchanged to create a review for the configuration you just viewed. Alternatively, you can use the dropdown to pick any saved review configuration. 6. **Assign Reviewers**: * Choose users from the list to assign them as reviewers for all rows. If the configuration includes reviewer notifications, notification emails will be dispatched on review publication. 7. **Set Due Date**: * Pick the date the review will finish. Reminder emails can trigger on, before, and after the due date depending on the notification settings in the configuration. 8. **Labels** (Optional): * Assign labels to this review so you can filter it by compliance program, business unit, environment, or review cycle. The review inherits any labels from its configuration, and you can add labels specific to this review. Applications are assigned on the configuration, not on an individual review. See [Labels and Applications for Access Reviews](/4yItIzMvkpAvMVFAamTf/features/access-reviews/configuration/labels-and-applications.md). 9. **Review Intelligence**: * By default, choose actions to automatically apply decisions to rows that were approved or rejected in the last review for the configuration. If an administrator has added additional [Review Intelligence Policies](/4yItIzMvkpAvMVFAamTf/features/access-reviews/configuration/review-intelligence-rules.md), you can enable them here. 10. **Time Frame Options**: Use this section to review access at a particular point in time, or based on Veza's latest graph data: * **From the moment the review is created**: Uses the most recently parsed integration data, including any changes since the last daily snapshot. * **From the most recent daily snapshot**: Uses Veza's most recent snapshot (which might be different from the latest data). * **From another snapshot**: Choose Graph data from a previous date. Use this option to review access at a specific point in time. 11. **Data Source Status**: Under **Time Frame Options**, click **Data Source Status** to view details for the chosen snapshot. Use this option to check if an important integration is inactive or reporting errors. 12. Select **Create Review**, then select **Save as draft**, **Publish now**, or **Publish later**. For drafts, see [Draft Reviews](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/draft-review.md). For **Publish later**, see [Schedule a draft to publish later](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/draft-review.md#schedule-a-draft-to-publish-later). ### See also * [Schedule an Access Review](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/schedule-access-review.md) * [Draft Reviews](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/draft-review.md) * [Create a Configuration](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/review-configuration.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/how-to/create-access-review.md?ask=&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.