> 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/draft-review.md).

# Draft Reviews

Create reviews as drafts to ensure that results are as expected, act on rows, and make changes to reviewers before notifying participants.

### Overview

Operators can choose to create access reviews in an unpublished, draft state. When a review is in a draft state, it offers an opportunity for the operator to inspect the included rows and adjust default reviewer assignments before commencing the review and notifying reviewers and other stakeholders.

Notes:

* Reviews must be explicitly published. When creating a new review, operators can create the review, which will save the review as a draft, or create and publish the review.
* Reviewers cannot view any unpublished reviews, even when they contain rows assigned to them.
* Operators can act on any results in unpublished reviews, including approving or rejecting, assigning reviewers, and signing off. Veza does not send webhooks for reviewer assignments when reviews are in draft state. All other webhooks (such as actions configured to trigger on rejected row sign-off) will trigger as normal.
* Publishing the review sends notification emails triggered "On review start."

### Create a review as a draft

1. Create an access review: [Create a Review](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/create-access-review.md).
2. When creating the review, click Create (instead of Create and Publish) to create the review in a draft state.

Reviews can also start as drafts without being created by hand:

* On a review schedule, select **Save as draft** under **Review creation** so every run the schedule creates starts as a draft. See [Schedule an Access Review](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/schedule-access-review.md).
* On a Lifecycle Management [Create Access Review](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/policies-workflows/actions/create-access-review.md) action, set **Creation Mode** to **Create as a draft**.

### Draft review actions

Operators can make changes to draft reviews without notifying assignees. To prepare a review, you might:

* Use the **Review Details** sidebar on the left to configure review-specific email notifications and Veza Actions.
* Add row-level reviewers with the **Reassign reviewers** action.
* Approve or reject rows you can immediately decide on.
* Add notes for other reviewers.
* Sign off on one or more rows using the **Sign-Off Selected** button at the top right.

### Publish a draft review

Review owners can publish drafts directly from the **Access Reviews** page:

1. Search for the draft review and click **Publish**.

   ![Publishing a draft access review.](https://1967633068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZDkWMxox3pekd0NsZJ%2Fuploads%2Fgit-blob-de3327bef1016523b00abfae4c65c7f67e062767%2Faccess-reviews-publish.png?alt=media)

To see active reviews and publish any drafts for a specific configuration:

1. Go to the **Configurations** page.
2. Use the search bar to find the configuration containing the review, and click to view **Configuration Details**.
3. In the **Active Reviews** section, find the draft review. Click **Publish**.

   ![Viewing and managing reviews for a configuration.](https://1967633068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZDkWMxox3pekd0NsZJ%2Fuploads%2Fgit-blob-cab2c809c9c32bff7b0f55c1b18185e6bb4add72%2Factive-reviews-publish.png?alt=media)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.veza.com/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/draft-review.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.