> 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/investor-interface/deposits.md).
# Deposits
## Deposit Request
### Creation
The Investor Interface allows investors to manage their deposits requests. \
\
After entering the desired amount, the investor must first **approve the transaction**, which grants permission for the Vault Owner or Admin to execute the request at a later stage.
Next, the investor must **confirm the operation** to finalize the request.
Both steps are on-chain transactions.
### Management
Once a deposit is submitted, it is added to the **Deposit Queue** and awaits processing by the Vault Owner or Admins.
Deposit requests can be cancelled by the investor at any time, unless the Vault Owner has defined a minimum holding period.
Investors can view their Pending and Executed Deposit Requests directly in the Investor Interface.
### Allowlist
If an allowlist has been set up, Enzyme.Onyx will verify the depositor’s wallet address and block any transaction from addresses not included on the list.
### Synchronous Deposits
Synchronous deposits can be configured in two ways:
* **As an additional mechanism** used alongside the standard deposit queue, giving depositors both options.
* **As a full replacement :** the standard deposit queue is disabled entirely, and all deposits go through the synchronous path.
The deposit queue and synchronous deposits operate independently. Deposit assets can differ between both methods, allowing managers to define distinct subscription paths with asset sets tailored to each deposit route.
---
# 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.enzyme.finance/onyx-user-documentation/investor-interface/deposits.md?ask=&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.
