> 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/cloud/es/concepts/intermediate-concepts/tags.md).

# Etiquetas

Las etiquetas de Devolutions Cloud le permiten clasificar entradas por proyecto, entorno o propietario para filtrar, buscar y generar informes por cliente.

Las etiquetas son sencillas marcas que se adjuntan a las entradas para organizarlas, filtrarlas y elaborar informes sobre ellas en bóvedas y carpetas. A diferencia de las estructuras de carpetas, una sola entrada puede tener varias etiquetas, lo que facilita agrupar elementos por proyecto, entorno o propietario.

Cuando se utiliza Devolutions Cloud con Remote Desktop Manager, las etiquetas asignadas en Devolutions Cloud son visibles en el cliente y pueden usarse en búsquedas avanzadas, informes y listas de reproducción. Un caso de uso típico consiste en etiquetar las entradas por nombre de cliente y entorno, de modo que los administradores puedan generar rápidamente informes o listas de reproducción por cliente sin modificar la estructura física de la bóveda.

#### Temas relacionados

* [Gestión de etiquetas](https://docs.devolutions.net/rdm/es/ribbon-menu-bar/edit/tag-management)


---

# 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 dynamically 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/cloud/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 `build a script that syncs our docs to a CMS` 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.