> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/knowledge-base/tenants/reset-a-tenants-administrative-password.md).

# Reset a Tenant's Administrative Password

Step-by-step instructions for resetting the administrative password for a tenant environment in VergeOS.

If you need to change the administrative credentials for a tenant environment in your VergeOS system, follow these steps:

1. Log in to the VergeOS environment where the tenant is hosted.
2. Navigate to the **Tenant Dashboard** of the tenant for which you need to change the admin password.
3. In the **Tenant Dashboard**, click the **Edit** button in the left navigation menu. This will open the Tenant Edit screen.
4. In the Tenant Edit screen, type the new password in the **Admin User Password** field.
5. Re-enter the password in the **Confirm Admin User Password** field.
6. After entering the same password in both fields, click **Submit**. If the passwords do not match, an error message will appear.
7. After successfully updating the admin password, open a web browser and navigate to the tenant environment where the password was changed.
8. Log in as the admin. The username will be **admin** and the password will be the new password you saved in step 6.

***

{% hint style="info" %}
**Document Information**

* Last Updated: 2024-08-29
* vergeOS Version: 4.12.6
  {% endhint %}


---

# 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.verge.io/knowledge-base/tenants/reset-a-tenants-administrative-password.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.
