> 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/enzyme-vault/subscription/control.md). # Control Enzyme Vaults provide flexible mechanisms for managers to define **who can invest, transfer shares, or interact with the Vault**. These controls allow Vaults to meet regulatory, compliance, or business-specific requirements while still leveraging the openness of blockchain infrastructure. ## Vault Share Transferability Vault Owners can configure the Vault Shares transferability to: * **Enable free transferability** → Shares can be traded or transferred like any other ERC20 token. * **Disable transferability** → Shares remain bound to the depositing address and cannot be moved. ## Whitelisting Vault Owners can choose to restrict participation by enabling a **whitelist**. * Only wallet addresses explicitly added by the Vault Owner or Manager will be able to deposit into the Vault. * Whitelists can be updated dynamically, giving managers full control over investor onboarding. ## KYC / KYB Enzyme does not enforce KYC (Know Your Customer) or KYB (Know Your Business) at the protocol level. **However,** Vault Owners and Managers can request to deploy an extra layer, using the service provider of their choice. --- # 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/enzyme-vault/subscription/control.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.