> 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/manage-delegations.md).

# Manage Reviewer Delegations

### Overview

A reviewer delegation routes one reviewer's review assignments to another user (the delegate). Delegations are managed on the **App Settings** > **Reviewers** > **Delegate List** page.

A delegation is either open-ended (in effect from creation until it is removed) or scheduled with an optional start date, end date, or both. Use a scheduled delegation for planned absences such as PTO, parental leave, or a temporary handover. A reviewer can have only one delegation entry at a time; overlapping or stacked schedules are not supported.

### Add a delegation

1. Open **App Settings** > **Reviewers** > **Delegate List**.
2. Click **Add Delegate**.
3. Select the **Original reviewer** and the **Delegate**.
4. (Optional) Enable the **Schedule this delegation** toggle to set a window:
   * **Starts**: Leave unset to activate the delegation immediately, or set a date and time to activate it later.
   * **Ends**: Leave unset to keep the delegation open-ended, or set a date and time to deactivate it automatically.
   * **Timezone**: The timezone used to enter and display the start and end values. The stored values are absolute (UTC).
5. Click **Add delegate**.

The end date must be in the future; windows that have already closed are rejected on save.

### Edit, re-activate, or remove a delegation

Each row in the table has action buttons in the **Actions** column:

* **Edit** (Active and Upcoming rows) opens an **Edit Delegate** form pre-filled with the current values. Submit with **Save changes**.
* **Re-activate** (Expired rows) opens a **Re-activate Delegate** form with the schedule toggle on and the dates cleared. Choose a new start, end, or both, then submit with **Re-activate delegate**.
* **Remove** (Active and Upcoming) or **Delete** (Expired) deletes the delegation.

### Status semantics

The delegations table includes a **Status** column and a status filter:

* **Active**: The delegation has no schedule, or the current time falls within its window. Within seven days of the end date, the status badge shows a countdown — *Ends today* or *Ends in N days*.
* **Upcoming**: The delegation has a future start date and is not yet in effect. The status badge shows *Starts today* or *Starts in N days*.
* **Expired**: The delegation has a past end date and is no longer in effect.

The status filter groups delegations by base status (Active / Upcoming / Expired); countdown labels do not change which group a row belongs to.

### How delegations affect reviewer assignment

* Auto-assignment and suggested reviewers honor a delegation only while it is **Active**. Outside of an active window, assignments route to the original reviewer.
* Scheduling a delegation does not retroactively reassign rows already assigned to the original reviewer in an active review. The window affects only **future** assignments — for example, rows created when a new review is generated from a configuration after the delegation becomes active.

### Notifications and the deny list

Delegations no longer suppress digest notifications for the original reviewer. To stop notifications to a specific reviewer, add them to the [reviewer deny list](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/configure-notification-exclusions.md) — the deny list is now the only mechanism for suppressing reviewer notifications.

### Audit events

The following events are recorded in Veza Events when a delegation is created or removed:

* `ACCESS_REVIEW_DELEGATION_CREATED`
* `ACCESS_REVIEW_DELEGATION_DELETED`

Editing a delegation is recorded as a delete of the previous entry followed by a create of the updated entry.


---

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

```
GET https://docs.veza.com/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/manage-delegations.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.