> For the complete documentation index, see [llms.txt](https://docs.connect.jfrog.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.connect.jfrog.io/features-new-ui/account-management/organize-your-fleet/tag-devices.md).

# Tag Devices

Tags enable you to create sets of devices that belong to different JFrog Connect groups. You can then filter and perform actions on tagged devices. This page describes how to create tags.

A [tag](/features-new-ui/account-management/organize-your-fleet.md#tags) is a parameter you define to identify devices with unique attributes. Tags provide one of several ways that you can [manage your fleet](/features-new-ui/account-management/organize-your-fleet.md) JFrog Connect. For example, tags enable you to associate devices that belong to different groups within a project.&#x20;

You can use tags to mark one or more devices within a group or mark devices that belong to different groups. Once you have tagged some devices, you can filter on the tag name in order to view and perform actions on the tagged devices only.

Connect provides a high degree of flexibility in tagging. There is no limit to the number of tags you can create or the number of tags a device can have. In addition, Connect enables you to tag several devices at once, without limit.

{% hint style="success" %}
**Tip**: For a quick way to tag a single device, see [Tag a Single Device](/features-new-ui/account-management/organize-your-fleet/tag-devices/tag-a-single-device.md).
{% endhint %}

To tag one or multiple devices, do the following:

1. Go to the **Devices** page and [create a filter](/features-new-ui/devices/fleet-overview/filter-bar.md) that will display all the devices you want to tag. For example, if you want to tag some devices from Group A, a device from Group B, and several devices from Group C, ensure that all of these [groups](/features-new-ui/account-management/organize-your-fleet.md#groups) will be displayed. You can use any of the filter criteria available to create a display that is most useful for marking the devices.
2. On the left side of the Devices table, mark the checkboxes next to the devices that will be tagged. You can also mark all the devices displayed at once.

<div align="left"><figure><img src="https://content.gitbook.com/content/OX8HIrQ8f257lv49Od1Z/blobs/hAo061akrrkp4FkOIbPU/add-many-devices-to-group-nui-01.png" alt="" width="563"><figcaption></figcaption></figure></div>

3. Click **Edit Details**.

<div align="left"><figure><img src="https://content.gitbook.com/content/OX8HIrQ8f257lv49Od1Z/blobs/f3zAKFtH93h2NINPLuGQ/add-many-devices-to-group-nui-02.png" alt=""><figcaption></figcaption></figure></div>

4. In Edit Details, mark **Edit Tags** and choose **Add**. Enter the name of one or multiple tags separated by commas. If a tag already exists, you can enter the first few letters and then choose the name that appears in the list. Apply your changes.

## What’s New?

Learn how to [remove a tag](/features-new-ui/account-management/organize-your-fleet/tag-devices/remove-a-tag.md).


---

# 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://docs.connect.jfrog.io/features-new-ui/account-management/organize-your-fleet/tag-devices.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.
