> 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/lifecycle-management/policies-workflows/actions/create-access-review.md).

# Create Access Review

Automatically create access review campaigns during lifecycle events.

Automatically creates access review campaigns during lifecycle events. This action bridges Lifecycle Management with Veza Access Reviews, enabling automated certification workflows triggered by identity lifecycle changes.

{% hint style="info" %}
CREATE\_ACCESS\_REVIEW is a control-plane action that executes within the Veza platform. The action creates review campaigns asynchronously: first queuing the review, then creating it based on the defined certification plan.
{% endhint %}

**Example Use Cases:**

* Review contractor access 30 days after onboarding to ensure appropriate permissions
* Certify elevated permissions after role changes or promotions
* Trigger periodic access reviews based on employment anniversaries
* Automatically review access for high-risk roles or sensitive systems
* Create access reviews when users join specific departments or teams

## Action settings

The Create Access Review action editor contains the following settings, stored in the action's `certification_creation_plan` object:

| Setting               | Required | Description                                                                                                                    |
| --------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------ |
| Review Configuration  | Yes      | The Access Workflow (review configuration) where the certification is created                                                  |
| Review Name           | No       | Name of the certification. Supports attribute transformers (e.g., `Review for {name}`). Custom names appear in Dry Run results |
| Reviewers             | No       | Primary level reviewer assignment (manager, resource owners, or designated reviewers)                                          |
| Fallback Reviewers    | No       | Reviewers to assign if automatic assignment fails                                                                              |
| Review Duration       | Yes      | **Number of days to review**: time from certification start when reviews are due                                               |
| Creation Instructions | No       | **Publish immediately** (sends the review to reviewers on creation) or **Create as a draft** (requires manual publishing)      |

{% hint style="info" %}
**Early Access:** Multi-level approval (second and third level reviewers) is in Early Access and may require Veza support to enable.
{% endhint %}

## Testing the review name formatter

The **Review Name** field accepts attribute transformers, so the name a review receives depends on the identity that triggered the workflow. Test the formatter from the action editor before saving the policy.

1. In the **Review Name** section of the Create Access Review action, select **Test**.
2. In **Test Review Name Formatter**, enter a sample value for each attribute the formatter references. Veza detects the attributes in the formatter and displays one input for each. Timestamp attributes accept ISO 8601 or RFC 3339 values, such as `2026-01-31` or `2026-01-31T09:15:32Z`.
3. Select **Test Formatter**.

The generated name appears under **Formatter Output**. When the formatter produces more than one candidate value, the first four appear with an option to display the rest. If the formatter cannot be evaluated, the error replaces the output and **Save** stays disabled until you correct the formatter.

Selecting **Save** in the modal writes the edited formatter back to the action.

Veza evaluates the formatter on the server against the policy's current version, so results reflect the transformers and lookup tables that version defines. Conditional (`IF`) formatting is not available on this field.

## How It Works

1. A lifecycle event triggers a workflow containing the CREATE\_ACCESS\_REVIEW action
2. The action evaluates its settings against the identity that triggered the event
3. A review campaign is queued in Veza Access Reviews
4. The review campaign is created and assigned to the designated reviewers
5. Reviewers receive notifications to certify or revoke the identified access

## Event Notifications

CREATE\_ACCESS\_REVIEW generates two notification events:

| Event                          | Timing       | Description                              |
| ------------------------------ | ------------ | ---------------------------------------- |
| CREATE\_ACCESS\_REVIEW\_QUEUED | Immediate    | Sent when the review creation is queued  |
| CREATE\_ACCESS\_REVIEW         | Asynchronous | Sent when the review campaign is created |

You can configure email notifications or webhooks for both events to track review creation progress. See [Notification Templates](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/policies-workflows/lifecycle-management-notification-templates.md) for configuration details.

{% hint style="info" %}
LCM-triggered reviews have special behaviors including automatic exclusion of unchanged results and entity type matching requirements. See [Access Reviews from Lifecycle Management](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/policies-workflows/lcm-access-reviews.md) for complete behavior documentation.
{% endhint %}

**Related Topics:**

* [Access Reviews from Lifecycle Management](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/policies-workflows/lcm-access-reviews.md): Behavior, filtering, entity matching, and troubleshooting
* [Access Reviews documentation](/4yItIzMvkpAvMVFAamTf/features/access-reviews.md): Configuring certification plans and managing reviews
* [Access Profiles](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/profiles.md): Managing birthright entitlements included in reviews


---

# 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/lifecycle-management/policies-workflows/actions/create-access-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.