# Reviewer Reassignment Setting

Controls whether users acting as assigned reviewers can reassign rows to other reviewers.

* When enabled (the default), any user assigned as a reviewer on specific rows can reassign those rows.
* When disabled, assigned reviewers cannot reassign rows.
* **Administrators, Operators, and Reassigners always retain reassignment privileges**, regardless of this setting.

This setting can be configured globally for all reviews, or for specific review configurations by `workflow_id` parameter.

The fallback precedence is:

* **configuration-specific setting** → **global setting** → **default** (`ALLOWED`).

## Parameters

The request body accepts:

* `value` (string) — `ALLOWED` or `NOT_ALLOWED`
* `workflow_id` (optional string) — Specific review configuration ID to override global settings

| Value         | Description                                    |
| ------------- | ---------------------------------------------- |
| `ALLOWED`     | Assigned reviewers can reassign rows (default) |
| `NOT_ALLOWED` | Assigned reviewers cannot reassign rows        |

## Examples

Example request to disable reviewer reassignment globally:

```json
{
  "value": "NOT_ALLOWED"
}
```

Example request to disable reviewer reassignment for a specific review configuration:

```json
{
  "value": "NOT_ALLOWED",
  "workflow_id": "8ae1c414-3a76-46cb-950a-925316b3f264"
}
```

## Get Reviewer Reassignment Setting

Retrieve the current reviewer reassignment setting. Include the optional `workflow_id` query parameter to get the setting for a specific review configuration.

**Global Settings Request:**

```bash
curl -L 'https://your-organization.vezacloud.com/api/private/workflows/access/global_settings/allow_reviewers_to_reassign_rows' \
-H 'Authorization: Bearer YOUR_API_KEY'
```

**Configuration-Specific Request:**

```bash
curl -L 'https://your-organization.vezacloud.com/api/private/workflows/access/global_settings/allow_reviewers_to_reassign_rows?workflow_id=8ae1c414-3a76-46cb-950a-925316b3f264' \
-H 'Authorization: Bearer YOUR_API_KEY'
```

Example response:

```json
{
  "value": "ALLOWED"
}
```

## Set Reviewer Reassignment Setting

Update the reviewer reassignment setting globally or for a specific review configuration. Requires Admin or Operator role.

**Global Settings Request:**

```bash
curl -L -X PUT 'https://your-organization.vezacloud.com/api/private/workflows/access/global_settings/allow_reviewers_to_reassign_rows' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer YOUR_API_KEY' \
-d '{
  "value": "NOT_ALLOWED"
}'
```

**Configuration-Specific Request:**

```bash
curl -L -X PUT 'https://your-organization.vezacloud.com/api/private/workflows/access/global_settings/allow_reviewers_to_reassign_rows' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer YOUR_API_KEY' \
-d '{
  "value": "NOT_ALLOWED",
  "workflow_id": "8ae1c414-3a76-46cb-950a-925316b3f264"
}'
```

Example response:

```json
{}
```


---

# Agent Instructions: 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:

```
GET https://docs.veza.com/4yItIzMvkpAvMVFAamTf/developers/api/workflows/access-review-settings/reviewerreassignmentsetting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.