> 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-protocol/user-roles.md). # User roles ## Management ### Owner Each Onyx instance has one owner. The owner must be fully-trusted. The owner can add/remove "admin" users. Owner is generally given permission to perform any "admin" action. Ownership is transferrable. ### Admin An Onyx instance can have multiple admins, set by the Owner. Each admin must be fully-trusted. Admins can generally perform any administrative action, other than, e.g., adding/removing admins. Admin role is non-transferrable. ### Limited admin roles To synthetically create scoped trust-throttled roles, peripheral contracts can be added as "admin" that define their own rules for allowed callers and callees. ## Shares holders By default, any account can deposit for, redeem, and transfer Shares, which are ERC20 representations of value held across on- and off-chain accounts. Share holders can be restricted by admins (i.e., who can deposit and receive transfers or any other limitation). Trust of share holders may vary depending on specific setups, but generally they are treated as untrusted. --- # 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-protocol/user-roles.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.