> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/es/concepts/intermediate-concepts/tags.md).

# Etiquetas

Las etiquetas en Devolutions Server son rótulos asociados a las entradas que crean agrupaciones de muchos a muchos entre carpetas y bóvedas para un filtrado rápido.

Las etiquetas en Devolutions Server son rótulos sencillos que se asocian a las entradas para agruparlas de forma lógica entre carpetas y bóvedas. A diferencia del árbol fijo de carpetas, las etiquetas permiten relaciones de muchos a muchos, como marcar la misma entrada como «Producción», «Linux» y «Cliente A».

Los usuarios pueden filtrar vistas y búsquedas por etiqueta para encontrar rápidamente elementos relacionados, independientemente de su ubicación física en la estructura. Por ejemplo, un auditor podría buscar todas las entradas etiquetadas como «Privilegiado» en varias bóvedas para revisar los controles de acceso y las prácticas de rotación.

#### Temas relacionados

* [Buscar](/server/es/web-interface/search.md)
* [Entradas](/server/es/web-interface/vaults/entries.md)


---

# 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.devolutions.net/server/es/concepts/intermediate-concepts/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.