Skip to content
Customer Portals are now available!Get Started
API Documentation was updated!Learn more

Tags

Device tags are labels you use to categorize, filter, and organize devices in a tree structure. Unlike work order and case tags, device tags support a parent-child hierarchy — letting you arrange devices along your own structure (e.g. site → hall → line).

For an overview of all tag types, see Workspace > Tags.

  • Workspace-wide — Device tags belong to the workspace and are available across all deployments.
  • Hierarchical — Each tag can be assigned a parent tag (“belongs to”). This forms a tree.
  • Many-to-many — A device can be assigned multiple tags, and a tag can hold multiple devices.

Each device tag has a name and an optional description.

  1. Open Workspace Settings > Workspace Tags and select device tags
  2. Create a new tag with a name (and optional description)
  3. Under “belongs to”, pick a parent tag to place it in the tree — or leave it empty for a top-level tag

Repeat to build your hierarchy. Tags without a parent form the roots of the tree; every other tag is nested under its parent.

You can assign devices directly from device tag management: select a tag and add one or more devices. Since assignment is many-to-many, a device can appear in multiple branches of the tree at once.

In the device tag view you navigate the tree column by column: select a tag to show its child tags and the devices assigned directly to it. Drill down through child tags until you reach the devices you need. Clicking a device opens its device record.

This makes it quick to narrow down to the right area even with many devices.

In the device list you can filter by device tags (alongside deployment, manufacturer, model, and connection status). See Managing Devices.

Example A — by organizational structure:

Site Berlin
├── Hall 1
│ ├── Line A
│ └── Line B
└── Hall 2
└── Line C

Devices are assigned to the matching leaf tag (e.g. “Line A”) and found via the tree.

Example B — by property:

Drive type
├── Differential drive
└── Omni drive

Here you structure devices by a technical property instead of location. Because assignment is many-to-many, a device can appear in both a location tree and a property tree.

  • Name consistently — Establish a convention for your tag hierarchy and share it with your team.
  • Keep it shallow where possible — Very deep trees make navigation harder.
  • Tidy up regularly — Remove unused tags.