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

# Mærker

Mærker i Devolutions Cloud giver Dem mulighed for at mærke poster efter projekt, miljø eller ejer, så De kan filtrere, søge og generere rapporter pr. kunde.

Mærker er enkle etiketter, som De knytter til poster for at organisere, filtrere og rapportere på dem på tværs af bokse og mapper. I modsætning til mappestrukturer kan en enkelt post have flere mærker, så det er nemt at gruppere elementer efter projekt, miljø eller ejer.

Når Devolutions Cloud bruges sammen med Remote Desktop Manager, er mærker, der er tildelt i Devolutions Cloud, synlige i klienten og kan bruges i avancerede søgninger, rapporter og afspilningslister. Et typisk brugsscenarie er at mærke poster efter kundenavn og miljø, så administratorer hurtigt kan generere rapporter eller afspilningslister pr. kunde uden at ændre den fysiske boksstruktur.

#### Relaterede emner

* [Administration af mærker](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/da/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.