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

# Trackers

The **Trackers** page of the Admin Panel provides comprehensive information on GPS device setup with a specific focus on configuring devices for optimal performance. Whether it's setting up new trackers or managing existing ones, the Admin Panel equips you with the necessary tools to efficiently handle device configurations.

<figure><img src="/files/NM62qvrbf5YkQ5gMczvY" alt="Trackers page"><figcaption><p>Trackers page</p></figcaption></figure>

The page consists of three main sections:

* **Tracker toolbar:** A toolbar used to easily find, edit, delete, export, or clone a tracker or change its owner.
* **Tracker list:** A list of all GPS devices currently registered in the Navixy instance. Each tracker is identified by its ID, title, status, model, device ID, phone number, and activation date.
* **Tracker details:** Information about a selected tracker with a list of related actions. See [Tracker details and operations](/docs/admin/devices/basic-operations.md#tracker-details) for more information.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://navixy.com/docs/admin/devices.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
