> For the complete documentation index, see [llms.txt](https://docs.mobiusflow.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mobiusflow.com/help/mobiusflow-v3/mobiusflow-toolbox-v3/tags.md).

# Tags

What are tags and how do I use them?

Tags are a powerful way to organise your objects and resources making it easier to find and group similar pieces of data.

Tags can be a simple key word or phrase (much like a hashtag in social media apps) or a keyword or phrase with an associated value.

Tags can be added to [object profiles](/help/mobiusflow-v3/mobiusflow-toolbox-v3/object-profiles.md) and individual [object](/help/mobiusflow-v3/mobiusflow-toolbox-v3/objects.md) instances. Any tags added to an object profile will be automatically added to all objects created from that profile.

The process of managing tags on object profiles, objects, and their resources is the same. To view the tag editor select an object profile, object, or resource and the relevant sidebar will open showing the tag editor. Once the sidebar is open follow the steps below.&#x20;

{% hint style="warning" %}
Remember to click **Save** after making any changes
{% endhint %}

<figure><img src="https://241296614-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQoV8xVJhcESUhdKQWDcm%2Fuploads%2F8ZlbirMtyc44tYS9SAjN%2FObject%20Profile%20Editor.png?alt=media&amp;token=ff6aefce-403b-4f0f-bc5e-863a8d6d2300" alt="" width="563"><figcaption></figcaption></figure>

## Adding tags

{% hint style="success" %}
Tag names are case sensitive can have spaces so `air_quality`, `air quality` and `Air Quality` are all valid tag names but are deemed different tags
{% endhint %}

### Adding a simple tag

In the **Add a tag** textbox type in the tag name and press **Enter**

The new tag will appear in the tag list

<figure><img src="https://241296614-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQoV8xVJhcESUhdKQWDcm%2Fuploads%2FzupBuNOpORU0lmLdFlqC%2FTags%20example%201.png?alt=media&amp;token=67d626b3-c838-4fb4-87c4-8dbd08d21a29" alt=""><figcaption></figcaption></figure>

### Adding a tag with value

In the **Add a tag** textbox type in the tag name followed by **=** and then the value e.g `floor = 1`

Press **Enter** and the tag will appear in the tag list

{% hint style="info" %}
You do not need to add a space either side of the equals sign. All white space will be stripped away
{% endhint %}

<figure><img src="https://241296614-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQoV8xVJhcESUhdKQWDcm%2Fuploads%2Fcji5fShmwxqOsx2eiIvD%2FTags%20example%202.png?alt=media&amp;token=d0d63d27-5344-4282-84c9-53daa7f27aff" alt=""><figcaption></figcaption></figure>

Tags with values will show the first five characters of the value but you can hover over the tag to see the full value

## Modifying a tag value

To modify the value of a tag or add a value to a simple tag just re-enter the tag name and value

To convert a value tag into a simple tag re-enter the tag name with no value&#x20;

## Deleting a tag

To delete a tag click on the **X** to the right of the tag in the tags list

## 💥 Interactive Demo

{% embed url="<https://demo.mobiusflow.com/demo/cmi7biyva4x4ub7b4uv3vh8xm?utm_source=link>" %}


---

# 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.mobiusflow.com/help/mobiusflow-v3/mobiusflow-toolbox-v3/tags.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.
