> 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/enzyme-blue-protocol/users/administrators.md).

# Administrators

There are two primary parties who administrate privileged functions in Enzyme Protocol: Avantgarde Core (deployer) and the Enzyme Council (admin).

## Avantgarde Core (deployer)

As the lead developer of the protocol, Avantgarde Core deploys all contracts, and configures all of them prior to taking a release live. Once the release is taken live, full access control of protected functions is handed over to the Enzyme Council.

This procedure will be detailed in a later section.

## Enzyme Council DAO (admin)

The Enzyme Council DAO is made up of two sub-committees; the Enzyme Technical Council (ETC) and the Enzyme Exposed Businesses (EEB). The ETC is a confederation of technically skilled appointed parties who together have sole access to voting on all protected, protocol-wide functions once a release is taken live.

The Enzyme Council is a fully trusted entity, which is core to the security assumptions of the protocol.


---

# 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/enzyme-blue-protocol/users/administrators.md?ask=<question>&goal=<user_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.