> 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-enzyme-vaults/vault-settings/delegation.md). # Delegation ### Ownership and delegation The Vault Owner has the highest level of admin control and access. They can grant (or remove) permission to third parties (Asset Managers) to trade on behalf of the vault. {% hint style="warning" %} **Asset Managers are fully trusted.** Asset Managers are treated as fully trusted actors, at the same level as the Vault Owner. Only add an address as an Asset Manager if you would trust it with the same level of control as the Vault Owner, and remove any Asset Manager you no longer fully trust. Policies can still restrict what an Asset Manager can do, but they are operational guardrails, not protection against a malicious or compromised Asset Manager. See [End users](https://docs.enzyme.finance/enzyme-blue-protocol/users/end-users#asset-manager) for details. {% endhint %} Policies can be used to keep Asset Managers within the vault's mandate, e.g., by limiting which integrations they can use or how much slippage their trades can incur. The policies can either be set when creating the vault or added at a later date. ### Delegated Trader In order to assign trading permisions to one (or more) addresses, go to Settings > Asset Management > Asset Managers, click on the button to "Add Asset Managers". Enter the Ethereum address and Add Managers and submit the transaction. Ask the multisig owners to log in with their address, connect via Wallet Connect and sign the pending 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-enzyme-vaults/vault-settings/delegation.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.