> 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/user/guide/devices-and-settings.md).

# Devices and settings

**Devices and settings** is where you configure each tracking device in your fleet. You pick a device from the list on the left, then adjust its behavior through a set of **settings blocks**: collapsible panels that each control one aspect of the device.

This section is for **fleet managers and administrators** who set up how devices report, what their sensors mean, when alerts fire, and how data flows to other systems. Use the cards below to jump to the group that matches your task.

{% hint style="warning" %}
The number of devices per account is restricted to 25,000, not including the deleted or hidden devices.
{% endhint %}

## How settings blocks work

* **Pick a device, expand a block, edit, and save.** Each block has its own save indicator. Some blocks offer a **Reset to defaults** button.
* **Not every block appears for every device.** The blocks you see depend on your **device model's hardware** (for example, a phone block only on devices with a SIM), your **plan** (some blocks require a plan feature), and your **permissions** (without edit rights, blocks appear read-only). Throughout this section, each block is described as *"appears if your device or plan supports it."*
* **Copy settings to other devices.** Many blocks let you apply their settings to one or more other devices at once, usually limited to compatible (same-model) devices.

{% hint style="warning" %}
Copying a block's settings **overwrites** the target devices' current settings for that block. **Blocked devices** show only the Phone number block, and nothing else is editable until the device is unblocked.
{% endhint %}

## Explore the section

<table data-card-size="large" data-view="cards"><thead><tr><th>Group</th><th>What it covers</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4>Managing devices and groups</h4></td><td>Search, filter, and organize the device list with tags and groups.</td><td><a href="/pages/7j8jhCyKcn638NC7arhe">/pages/7j8jhCyKcn638NC7arhe</a></td></tr><tr><td><h4>Object management</h4></td><td>Device identity and admin: label, group, tags, SIM, plan, statuses, and commands.</td><td><a href="/pages/WoAji3vSZjq6TfaTdF7s">/pages/WoAji3vSZjq6TfaTdF7s</a></td></tr><tr><td><h4>Location and movement</h4></td><td>How the device reports position: tracking, parking, odometer, ignition, and towing.</td><td><a href="/pages/R3W4dXezTjJal9OmxBGZ">/pages/R3W4dXezTjJal9OmxBGZ</a></td></tr><tr><td><h4>Vehicle sensors</h4></td><td>Turn raw inputs into fuel, temperature, ignition, and other sensor values.</td><td><a href="/pages/2QBjKApe18OQTG89w3pP">/pages/2QBjKApe18OQTG89w3pP</a></td></tr><tr><td><h4>Connectivity</h4></td><td>Offline timeout and data forwarding to third-party servers.</td><td><a href="/pages/LJhrmmvNx4wydTI8LX0j">/pages/LJhrmmvNx4wydTI8LX0j</a></td></tr><tr><td><h4>Driver safety</h4></td><td>Detect and report harsh acceleration, braking, and cornering.</td><td><a href="/pages/e6IS7EPOPs6sNUOksghB">/pages/e6IS7EPOPs6sNUOksghB</a></td></tr><tr><td><h4>Tachograph and compliance</h4></td><td>Download and email digital tachograph DDD files.</td><td><a href="/pages/obEvamG0HXnc7ppWVd6E">/pages/obEvamG0HXnc7ppWVd6E</a></td></tr><tr><td><h4>Device-specific controls</h4></td><td>Hardware-specific blocks that appear only on supported devices.</td><td><a href="/pages/C7lXyd1bJQ83AInsW8LW">/pages/C7lXyd1bJQ83AInsW8LW</a></td></tr></tbody></table>


---

# 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/user/guide/devices-and-settings.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.