Start Free Trial

Tags

Tags are simple key:value labels you attach to devices so you can group, find, and filter them. A tag like Location:Los Angeles or floor:3 turns a long device list into something you can slice by site, role, owner, or anything else you care about. You create tags once, then reuse them across many devices.

The mental model: a tag is a reusable label that lives at the account or application level. You define it once (a Tag Name and a Tag Value), assign the same tag to as many devices as you like, then filter the Devices list by it. Today, devices are the only thing you tag.
Diagram: a single Tag made of a key and a value, for example Location colon Los Angeles, is assigned to several devices through a many-to-many link. The same tag then appears as a filter on the Devices list, narrowing it to just the devices that carry that tag.
How tags work: define a key:value label once, assign it to many devices, then filter by it.

Quick Start

The short version for people who already know NEQTO.ai.

  • 1
    Open Tag Management and click Create Tag. Enter a Tag Name (the key, for example Location) and a Tag Value (for example Los Angeles).
  • 2
    Open a device (or the Add Device form) and pick the tag from the Tags field. One device can carry many tags.
  • 3
    Go to the Devices list and use the Tags filter to narrow it down. Pick several tags and the list shows only devices that have all of them.

What a Tag Is

Every tag is a pair: a Tag Name (the key) and a Tag Value. Both are required, both are free-form text.

PartUI labelRequiredLimit
KeyTag NameYesUp to 25 characters.
ValueTag ValueYesUp to 25 characters.
  • Free-form text. Both fields accept any text up to the limit. Leading and trailing spaces are trimmed.
  • Uniqueness. You cannot create two identical tags in the same scope. A tag is a duplicate when its Tag Name and Tag Value match an existing one within the same account (and same application, if you are working inside an application). Try it and you get a “Tag with this key and value already exists for this organization.” error.
  • Reuse the same key. Because uniqueness is on the full pair, Location:Los Angeles and Location:Tokyo are two separate tags. That is the intended way to build out a dimension like “Location”.
Heads up on allowed characters. The Create Tag form shows placeholders like e.g., Location and e.g., Los Angeles, and it only enforces two things: both fields are required, and each is 25 characters or fewer. There is no character restriction in the live form, so spaces and any other characters are accepted in both Tag Name and Tag Value. Keep names short and consistent anyway.

Tag Management

Tag Management is the dedicated screen for creating, editing, and deleting your tags. The page title is Tag Management and it explains itself: “Tags help you organize and filter your devices more easily.”

Tag Management list shown as a table. Columns are Tag Name, Tag Value, Created on, Account, and Application. A search box sits above the table, a Create Tag button is in the header, and each row has an actions menu with Edit and Delete.
The Tag Management list. Each row is one key:value tag you can reuse across devices.

The list view

ColumnWhat it shows
Tag NameThe key, shown in the highlight colour.
Tag ValueThe value.
Created onThe date the tag was created.
AccountThe account the tag belongs to.
ApplicationThe application the tag is scoped to, or a dash for account-level tags.
  • Search filters the list by Tag Name or Tag Value (case-insensitive, matches anywhere in the text).
  • Sort by any column, including Created on, Account, and Application.
  • Paginated at 10 rows per page by default.
  • Column widths are resizable and your choice is remembered.

Account-level vs. application tags

Tag Management appears in two places, and the list is scoped differently in each:

Where you open itWhat you seeNew tags are
The top-level Tags pageOnly account-level tags (not tied to any application).Account-level.
Inside an applicationThat application’s tags plus the account-level tags.Scoped to that application.
Why this matters: a tag created inside an application is visible only within that application (and on the device tools there). Account-level tags are visible everywhere. If you want a tag you can use across all applications, create it from the top-level Tags page.

Create a tag

Create Tag modal with two fields: Tag Name with placeholder text reading e.g. comma Location, and Tag Value with placeholder text reading e.g. comma Los Angeles. Buttons read Cancel and Create.
Creating a tag. Both Tag Name and Tag Value are required.
  • 1
    Click Create Tag.
  • 2
    Enter a Tag Name and a Tag Value. Both are required and each is limited to 25 characters.
  • 3
    Click Create. A “Tag created successfully” confirmation appears and the tag joins the list.
Tags empty state showing a heading No tags created yet, the line Start organizing your devices with custom tags, and a Create Tag button with a plus icon.
Before you have any tags, the screen invites you to create your first one.

Edit a tag

Use the row’s actions menu and choose Edit. You can change the Tag Name and Tag Value; the same length and uniqueness rules apply. Editing a tag updates it everywhere it is assigned, so a single change re-labels every device that carries it.

Delete a tag

Delete Tag confirmation dialog. It asks Are you sure you want to delete the tag, names the tag as key colon value, and warns This will unassign it from all devices. Buttons read Cancel and Delete.
Deleting a tag also removes it from every device it was on.

From the actions menu choose Delete. The confirm dialog spells out the consequence: “This will unassign it from all devices.” Deleting a tag detaches it from every device that had it. The devices themselves are untouched; they simply lose that one label.

Permissions. Creating, editing, and deleting tags are separate permissions. If your role lacks them, the Create Tag button and the Edit/Delete actions do not appear. Read access is enough to see and filter by tags.

Assigning Tags to Devices

Today, you assign tags to a device from its General Info section, not while creating it. The Add Device wizard focuses on choosing a device endpoint and detecting the device; the Tags field appears once the device exists.

When adding a device

The current Add Device wizard does not include a Tags step. It walks you through picking a device endpoint and detecting the device; tagging happens on the device itself, once it exists.

On an existing device

Device detail General Info tab showing a Tags field. Assigned tags appear as info-coloured badges, and a searchable input lets you add more tags or create a new one inline when no match is found.
General Info shows assigned tags as badges and lets you add or remove them.

Open a device and go to General Info. The Tags field shows what is assigned and lets you add or remove tags. If none are assigned it reads “No tags assigned”.

Create a tag on the fly. If you search the device’s Tags field and nothing matches, you can create a new tag right there without leaving the device. The new tag is created (scoped to the application if you are inside one) and assigned in one step.
  • Many-to-many. A device can have many tags, and a tag can be on many devices. The same tag is shared, not copied, so editing it updates every device at once.
  • One assignment per pair. A given tag can be on a device only once; you cannot add the same tag twice to one device.
  • Removing a tag from a device only detaches it from that device. The tag itself stays in Tag Management for reuse.

Filtering Devices by Tag

This is the payoff. Once devices are tagged, the Devices list can be narrowed to just the ones you want.

Devices list with a Tags column. Each device shows its tags as small badges with the key in a lighter shade above the value, displaying up to three tags and a plus N more indicator for the rest. A Tags filter control above the list lets you pick one or more tags to narrow the table.
The Devices list. The Tags column shows each device’s labels, and the Tags filter narrows the list.
  • Tags column. Each device row shows its tags as badges (key above value). If a device has more than three, the extras collapse into a +N more indicator.
  • Tags filter. A filter control above the list lets you choose one or more tags. The options are your existing tags, shown as key:value.
  • Multiple tags use AND. Select several tags and the list shows only devices that have every selected tag, not any of them. To see devices matching either tag, filter one at a time.
  • Shareable URL. The active tag filter is written into the page address (a tags parameter), so a filtered Devices view can be bookmarked or shared and it reopens already filtered.
Note on the filter control. The Tags filter only appears when the Tags column is visible and at least one tag exists. If you have hidden the Tags column, bring it back from the column-visibility control to get the filter.

What Tags Do and Don’t Drive

Tags are deliberately focused. Here is what they currently affect.

AreaDo tags apply?
Tagging devicesYes. Devices are the only entity you can tag.
Filtering the Devices listYes. The main use of tags.
Endpoints, dashboards, alerts, maps, analyticsNo. These are not tagged and are not grouped or scoped by tags today.
Application scopingIndirect. A tag can be account-level or scoped to one application, which controls where it is offered, but a tag does not assign a device to an application.
Not a hierarchy or a search syntax. Tags are flat key:value pairs. There are no nested tags, no wildcard matching, and no free-text tag query. To organize across a dimension, reuse one Tag Name with different values (for example site:warehouse-A, site:warehouse-B).

Limits and Good to Know

Limit / behaviorDetail
Tag Name length1 to 25 characters, required.
Tag Value length1 to 25 characters, required.
UniquenessThe full Tag Name + Tag Value pair must be unique within its scope (account, and application when set).
Tags per deviceNo fixed cap; the list view shows the first three and folds the rest into “+N more”.
ScopeAccount-level (visible everywhere) or application-scoped (visible inside that application plus account-level tags).
Delete behaviorUnassigns the tag from all devices. Devices are not deleted.
  • Plan it like a dimension. Decide your Tag Names up front (Location, Site, Owner, Role) and keep values consistent. Tidy tags make the Devices filter genuinely useful.
  • Account-level for shared labels. Create tags you want everywhere from the top-level Tags page; create app-specific ones from inside the application.
  • Editing is global. Renaming a tag re-labels every device that carries it, in one move.
  • Filtering is AND. More selected tags means fewer matching devices, not more.

Leave a Reply

Your email address will not be published. Required fields are marked *

Start Free Trial

Open external link

You’re leaving Claude to visit an external link:
https://stg-app.env-neqtoai-staging.kinsta.cloud/en/dashboards
Cancel
Open link