# Tags

Devices can be structured by annotating them with **tags**. This allows managing large amounts of **Assets** within a **Workspace** at once and brings more convenience by setting up [**Rules**](https://docs.akenza.io/akenza.io/get-started/rule-engine) that apply to multiple [**Assets**](https://docs.akenza.io/akenza.io/get-started/create-new-device). The following steps are explained in more detail:

{% hint style="info" %}
Asset Tags can also be used to filter or search for assets within the **Asset Inventory**.
{% endhint %}

### 1. Adding tags during device creation

A **tag** can be added optionally to a device during device creation. Already existing tags will be displayed on the tag field and can be selected if wanted. Otherwise, a new tag can be created by giving an individual name. Tag names are limited to **64 characters** and could stand for a group of sensors such as *Temperature, Humidity,* or *CO2* or for certain rooms or areas like *1st-floor building A*.

![Asset tags during device creation](https://2165942204-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MMKXTFIN5ZlLOjBlfC4%2Fuploads%2FTzwWjQZPGjTq3AfV77Ss%2Fscreely-1685031162904.png?alt=media\&token=83dd10cd-c765-4547-8106-144a2d8c98d4)

### 2. Adding tags on the device detail page

When adding tags to a device on the **device detail page** you can choose from the existing workspace tags or create a new tag. A device can have one or multiple tags. When tags are removed from a device, they are not deleted from the workspace.

![Asset tags on device detail page](https://2165942204-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MMKXTFIN5ZlLOjBlfC4%2Fuploads%2FLCU2vMRGnDp9FBkOidKf%2Fscreely-1685009736677.png?alt=media\&token=38d56e29-f5c8-4996-9fe5-037c254b5c41)

### 3. Managing tags on the workspace settings page

A **tag** can be added or edited on the Tag management page in the workspace settings. Already existing tags can be viewed and modified. A new tag can be created or a set of new tags can be imported using bulk import (see the template below). 

Tag names are limited to **64 characters** and have to be **unique within a workspace**. A tag can stand for a group of sensors such as *Temperature, Humidity,* or *CO2* or for certain rooms or areas like *floor1*.

A bulk import template for tags can be downloaded here:

{% file src="<https://2165942204-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MMKXTFIN5ZlLOjBlfC4%2Fuploads%2Fo5jGCnR5n1Z4vywx7Hww%2FTag%20bulk%20import%20template.csv?alt=media&token=0c6a8c6f-7d2e-44fa-bd5c-d602d5d6ca06>" %}

### 4. Use of tags as rule input

Tags can be used as **rule input** on the Rule Engine. This simplifies the selection of a multiple devices that shall have the same rule logic applied. All existing tags in the **Workspace** are displayed on the Rule Input as A*vailable tags* and can be selected as a Rule Input.

{% hint style="warning" %}
To apply tags as a Rule Input, devices must have the same data schema (topic and data key)
{% endhint %}

![Tag as rule input](https://2165942204-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MMKXTFIN5ZlLOjBlfC4%2Fuploads%2FuNVCUuVJsRMciLPRuPHR%2Fscreely-1685031408334.png?alt=media\&token=375e4821-fb3a-4a4e-8d9e-a9527f4f04af)