> 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/concepts/intermediate-concepts/tags.md). # Tags Devolutions Cloud tags let you label entries by project, environment, or owner for filtering, searching, and generating per customer reports. Tags are simple labels that you attach to entries to organize, filter, and report on them across vaults and folders. Unlike folder structures, a single entry can have multiple tags, making it easy to group items by project, environment, or owner. When Devolutions Cloud is used with Remote Desktop Manager, tags assigned in Devolutions Cloud are visible in the client and can be used in advanced searches, reports, and playlists. A typical use case is tagging entries by customer name and environment so that administrators can quickly generate per customer reports or playlists without changing the physical vault structure. #### Related topics * [Tag management](https://docs.devolutions.net/rdm/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 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/concepts/intermediate-concepts/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.