> For the complete documentation index, see [llms.txt](https://docs.enzyme.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enzyme.finance/onyx-user-documentation/administration-app/vault/address-lists-management.md).

# Address Lists Management

An **address list** is an on-chain contract that holds a set of wallet addresses. Your vault uses these lists to control **who can do what** — for example:

* who may **send** or **receive** vault shares (transfer validation), or
* who may **deposit** through a deposit handler (deposit allowlist).

Address Lists appear only when they are **already connected** to your vault (transfer validator or a deposit handler). You manage **members** (add / remove addresses) on those lists.

### Address Lists Page

#### **When the page is empty**

You’ll see: *“No address lists are configured for this vault.”*

That means no list is currently referenced by:

* the shares **transfer validator** (sender or recipient list), or
* an **ERC-7540 deposit queue** external allowlist, or
* a **sync deposit handler** allowlist.

Lists are not shown just because they exist on-chain — they must be **wired to your vault**. To attach a new list or change which list is used, contact [Enzyme support](mailto:support@enzyme.finance)

#### **When lists appear**

\
Each list is shown as a **card** with:

<figure><img src="/files/Z29Sj9po6wACUx2jpS69" alt=""><figcaption></figcaption></figure>

1. **List contract address** — the on-chain list (with explorer link).
2. **List type badge**
   * **Ownable** — standard ownable list. The owner of this list can be any chosen arbitrary wallet.
   * **Shares owned** — list tied to vault shares; same add/remove actions in the UI. Any admin or owner of the shares can manage it.
3. **Usage badges** — what this list controls for *your* vault, for example:
   * **Transfer shares (sender)** / **(recipient)** — linked transfer validator
   * **Deposit queue** — ERC-7540 external allowlist
   * **Sync deposit handler** — sync handler allowlist

One list can have **multiple badges** if the same contract is used in more than one place.

#### **Managing members (add / remove)**

1. Open **Address Lists**.
2. Find the list (usage badges help you pick the right one).
3. **Add address** — use **Add Address** button (wallet must be the owner of the Address List; confirm on-chain). You'll be taken to a new page where you can add addresses in that address list either one at a time, or in batch by copy pasting addresses separated by commas. Once you paste addresses, click the **Load** button to confirm set of addresses and submit transaction to add them.

<figure><img src="/files/QjVf1D2qRajf2jUljRgy" alt=""><figcaption></figcaption></figure>

4. **Remove addresses** — select checkboxes (or trash on a row) → **Remove Addresses** → confirm. (wallet must be the owner of the Address List)

If you arrived from Deposit Requests with the **Address List** card, the correct list is **highlighted** and scrolled into view.

<figure><img src="/files/pKWt1H6GtH68Mj7OXCiY" alt=""><figcaption></figcaption></figure>

> ***Note:** Member addresses sync from the blockchain via the indexer. After a transaction confirms, the list may take a short time to update in the app.*


---

# 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.enzyme.finance/onyx-user-documentation/administration-app/vault/address-lists-management.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.