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

# Using Tags

Keep your projects and resources organized with our handy Tags feature!

You can use tags on all entities in Locoia to make them easier to search for and find.

Tags are shared and autosuggested across all entities; e.g. if you add the Tag "CRM & Sales" to a dashboard, it will also be shown as a suggestion on flows:

![Tag suggestions](https://291121471-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McrRFZHYH27bqKzOVDd%2F-MjUY4qL374YfLLr28J9%2F-MjUZ524UpkS501k4cYG%2Fimage.png?alt=media\&token=4e8e0b11-4b6f-4f95-a269-7e765804eb98)

On the overview pages you can then filter by these tags, e.g. as shown here on the Flow Builder overview:

![Filtering by tags](https://291121471-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McrRFZHYH27bqKzOVDd%2F-MjUY4qL374YfLLr28J9%2F-MjUZY5BCbfe2TbQUN8F%2Fimage.png?alt=media\&token=d650bac9-8473-41bd-9f19-5e776ce08d27)

{% hint style="info" %}
You can share your exact search with any other user that is part of your account by sending them your current URL, which includes the tag(s) selected by you.
{% endhint %}


---

# 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.locoia.com/best-practice-guides/using-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.