> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/hera604/diagnostics-and-maintenance/user-management.md).

# User Management

Secure administrator access.

#### Administrator password

Open **Diagnostics & Maintenance > User Management > Administrator password** to change the web-interface administrator password.

<figure><img src="https://333373795-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBMckwRPzYNvOiZyh1fl3%2Fuploads%2F41QuSLjOIkpP5LsnY3Lh%2FScreenshot%202026-08-14%20at%2016.59.53.png?alt=media&amp;token=869f4849-2451-4100-b160-90115b050653" alt=""><figcaption></figcaption></figure>

The username shown is `Hera604User` and cannot be edited on this page.

To change the password:

1. Enter the new password in **New password**.
2. Enter it again in **Confirm new password**.
3. Select **Save**.
4. Store the password in the organisation's approved credential manager.
5. Sign out and confirm that the new password works.

Use a unique password of at least 10 characters and follow the deployment's password policy. Do not include the password in tickets, screenshots, or site notes.


---

# 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.eseye.com/hera604/diagnostics-and-maintenance/user-management.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.