> 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/developers/api/workflows/clonereviewconfiguration.md).

# Clone Review Configuration

## Overview

Duplicates an existing access review configuration and assigns it a new name. Note that the API path uses the older term `workflow`. In the Veza UI, these are called **configurations** — as shown on the **Access Reviews > Configurations** page.

The clone inherits the source configuration's:

* Query and scope
* Notifications and Veza Actions
* Reviewer experience options — column selection and overrides, default sort order, row grouping, UI customizations, and reviewer export and bulk-action settings
* Review behavior — completion and expiration behavior, self-review prevention, mandatory due-date settings, and auto-complete rules
* Automation and alerting — digest notifications, review alerts, and any attached automations
* Limit Access list, when the [Permission Sets for Configurations and Integrations](/4yItIzMvkpAvMVFAamTf/administration/administration/access-controls.md) (Early Access) feature is enabled on the tenant

In short, any setting you can configure on a configuration in the builder is carried over to the clone.

Any reviews already created from the source configuration are not cloned. The new configuration starts with no reviews. The user calling the endpoint becomes the owner of the new configuration.

## Permissions

Available to users with the **Administrator**, **Access Reviews Admin**, or **Operator** role on the root team.

## API reference

{% openapi src="/files/Aco9gj4MY2XoNiD4zIjr" path="/api/private/workflows/access/{workflow\_id}:clone" method="post" %}
[openapi.yaml](https://1967633068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZDkWMxox3pekd0NsZJ%2Fuploads%2Fgit-blob-cc6281c14f1540c934b1093e311ed7cf96bd5aea%2Fopenapi.yaml?alt=media)
{% endopenapi %}

## Example request

```bash
curl -X POST "https://your-organization.vezacloud.com/api/private/workflows/access/{workflow_id}:clone" \
  -H "authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"name": "Q3 Finance Review (copy)"}'
```

## Example response

```json
{
  "workflow_id": "019ed153-9f4c-7d3c-85c9-f9d516be99c0"
}
```

Use the returned `workflow_id` to fetch the new configuration with `GET /api/private/workflows/access/{workflow_id}`, or to update it with subsequent API calls.


---

# 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/developers/api/workflows/clonereviewconfiguration.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.