> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/qna/on-premise/manage-admin-credentials-on-premise.md).

# Manage admin credentials (On-premise)

Rename admin account in the google.dealers table or reset password via API server. Log in to Admin Panel and use the password change feature

## Can I rename the admin account so that I can access Admin Panel using a login of my choice?

Yes, but this isn't recommended.

You can do this in `google.dealers` table, and you need to update the `login` value. The default value is `admin` and you can change it to whatever you need. Be sure to remember the updated login value.

## How do I change my Admin Panel password?

If you know your current password, log in to your account and then use the password change feature in the upper right corner.

If you have lost your current password, you need to reset it. This reset is done on the application server by directly contacting the API server. Follow the instruction below.

## Links

* [Password reset](https://www.navixy.com/docs/on-premise/on-premise/how-to-guide/maintenance/server-credentials/password-reset)


---

# 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://navixy.com/docs/qna/on-premise/manage-admin-credentials-on-premise.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.