> 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/admin/admin-panel.md).

# Admin Panel

Manage your Navixy dealer account: configure the GPS tracking platform, create user accounts, manage devices, and set up billing and reseller plans

Navixy Admin Panel is a powerful tool that allows administrators to customize the GPS tracking service platform and perform daily tasks to deliver high-quality commercial services to end-users. This section provides information on how to access the Navixy Admin Panel and the features available to you.

## Accessing Navixy Admin Panel

To access Navixy Admin Panel, use your login credentials at <https://panel.navixy.com/>. If you've forgotten your login or password, contact your personal account manager for assistance.

{% hint style="warning" %}
When creating an Admin Panel account, passwords must be between 12 and 20 characters in length and include at least one uppercase letter, lowercase letter, digit, and special character. To maintain account security, the system tracks password history, so you can't reuse any of your last 10 passwords. If a previous password is detected, the system will return the error: "Password was recently used."
{% 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 dynamically 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/admin/admin-panel.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 `build a script that syncs our docs to a CMS` 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.