> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/generalites/tags.md).
# Tag management
Tags allow you to classify information in Dastra in a simple and intuitive way
## What are tags for?
Tags are used to classify information according to your own methodology. They allow you to identify treatments or other elements in Dastra in order to make them stand out.
Thus, you can put a "priority" or "To be checked" or "sensitive treatment" tag to allow you to easily find the treatments or other elements concerned. The list of tags is not limited. You can put several tags on a treatment for example. By clicking on a tag, you will automatically filter the treatments that have this tag.
## How to create tags?
In the tag entry form, start typing the name of any tag, there are two possibilities, either the tag already exists, in which case you can select it. If it doesn't exist, you can press **the enter key on your keyboard**, which will create the new tag automatically to add it to the selection list.
## How to manage all the tags in the application?
Go to > **Workspace Settings** 
Click on the **Tag** menu in "Process"
---
# 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://doc.dastra.eu/en/features/generalites/tags.md?ask=&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.
