> 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/user-documentation/blue-investor-experience/deposit-and-redemptions.md).
# Deposit and Redemptions
#### Deposits
A key feature for both builders and managers is that if configured in such a way, Enzyme vaults can accept depositors. Those depositors will receive tokenized deposits known as vault shares.
Depositors can connect a wallet via the connect button on the top right hand side of the app.
Once connected, click the `Deposit` button in the top right corner of the Vault's page and follow the instructions from there signing approve and deposit transactions as guided.
Once you've completed either process above and the `Deposit` transaction is successfully mined, you are officially a vault token-holder. The app will take a moment to reflect the changes. See the [risks & nuances](https://app.gitbook.com/o/-M17sAWG26bbHj7WurKa/s/WzXrybpj5e9VBbPlbYCJ/~/changes/238/general-info/risks-and-nuances) section before depositing.
#### Withdrawals
Withdrawing from a Vault is relatively easy. Once connected with your wallet, go to the `Withdrawal` button and sign the transaction.
---
# 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/user-documentation/blue-investor-experience/deposit-and-redemptions.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.