> 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/general/tags.md).
# Tag management
Tags classify the information in Dastra according to your own method: creation, management, import and export.
## Purpose of tags
Tags classify information according to your own methodology. They let you flag processing activities or other elements in Dastra to make them stand out.
For example, you can add a "priority", "to be checked" or "sensitive processing" tag to find the elements concerned. The list of tags is not limited and you can put several tags on a processing activity. Clicking a tag filters the elements that carry it.
A tag belongs to one object type: tags of processing activities, requests, data breaches, tasks, stakeholders, measures, assets, risks, datasets, questionnaire templates, AI systems, AI models, contracts, controls and risk scenarios are managed separately. Each tag has a color.
## Create tags
In a **Tags** field, start typing the name of a tag. If it exists, select it. If it does not exist, press the **Enter** key: Dastra creates the tag and adds it to the selection. Only users with the advanced write permission can create a tag this way.
Typing a tag in a form
When the field is empty, an AI assistant button can suggest tags from the name and description of the object. See [Use cases](/en/features/general/ai-assistant/use-cases.md).
## Manage the tags of the workspace
1. In the sidebar, click **Workspace settings**.
2. In the **Process** section, click **Tags**.
3. Choose the object type whose tags you want to manage.
The list of tags of an object type
From this page, you can:
* click **Create a tag**, enter its **Tag label** and choose its **Color**;
* click the arrow of the button to **Create from library...**, **Import** tags from a file (see [Import your data](/en/features/general/import.md)) or **Export** the list as CSV, XLSX, JSON or Markdown;
* open the menu of a tag to **Edit tag**, **Delete** the tag or click **Related objects**, which opens the list of the elements that carry this tag;
* select several tags, then **Select a batch action** > **Delete**.
From a **Tags** field, the **Tags management** link at the bottom of the list opens the same list, limited to the object type of the form.
The **Process** section is only visible to users with the advanced write permission.
---
# 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/general/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.
