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

# Managing devices and groups

Find devices in the settings list by name or tag, and create, rename, color-code, and delete device groups to organize your fleet.

The device list on the left of **Devices and settings** is where you choose the device to configure and keep your fleet organized. As fleets grow, search, tags, and groups make it fast to find the right device and to apply settings consistently.

## Finding a device

* **Search by name**: Type in the search box to filter the list to matching device labels.
* **Filter by tag**: Narrow the list to devices carrying a selected tag.
* **Browse by group**: Groups expand and collapse, and their state is remembered between sessions.

## Managing groups

Groups let you organize devices by department, function, site, or any scheme that fits your fleet.

{% stepper %}
{% step %}

### Create a group

Add a new group and give it a name (up to **60 characters**) and a color so it stands out in the list.
{% endstep %}

{% step %}

### Rename or recolor

Edit an existing group's name (up to **60 characters**) or change its color at any time.
{% endstep %}

{% step %}

### Delete a group

Remove a group you no longer need. If the group still contains devices, you're prompted to move them to another group first so no device is left ungrouped.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Tags and groups are complementary: a device belongs to **one group** but can carry **multiple tags**. Use groups for primary organization and tags for cross-cutting filters.
{% endhint %}

## See also

* [Object label](/docs/user/guide/devices-and-settings/object-management/object-label.md): assign a device's group and tags.


---

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