> For the complete documentation index, see [llms.txt](https://docs.lenses.io/latest/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lenses.io/latest/devx/6.2/deployment/configuration/authentication/admin-account.md).

# Admin Account

This page describes how to configure admin accounts in Lenses.

You can configure a list of the principals (users, service accounts) with root admin access. Access control allows any API operation performed by such principals. If not set, it will default to **\[]**.

Admin accounts are set in the **config.yaml** for HQ under the [auth.administrators](/latest/devx/6.2/deployment/configuration/hq.md#authconfig) key, as an array of **usernames**.

{% code title="config.yaml" %}

```yaml
auth:
  administrators:
  - admin
  - brian.lifeof@lenses.io
  - bob.builder@lenses.io    
```

{% endcode %}

## Changing the Admin Password

To change the admin password, update the **config.yaml** in the [auth.users](/latest/devx/6.2/deployment/configuration/hq.md#authconfig) section. Set the password of the admin users.

{% hint style="success" %}
Passwords need to be bcrypt hashes.
{% endhint %}

You can use the Lenses CLI to create a bcrypt password. You can download the CLI [here](https://archive.lenses.io/lenses/6.1/). The executable for Lenses 6 CLI is called "hq".

```sh
hq utils hash-password
```

```yaml
auth:
  - admin
  - brian.lifeof@lenses.io
  - bob.builder@lenses.io
users:
  - username: admin
    password: $2a$12$XQW..XQrtZXCvbQWertqQeFi/1KoQW4eNephNXTfHqtoW9Q4qih5G 
```


---

# 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.lenses.io/latest/devx/6.2/deployment/configuration/authentication/admin-account.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.