> 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/powershell-universal/da/platform/tags.md).

# Mærker

Opret og administrer mærker i PowerShell Universal for logisk at gruppere relaterede ressourcer og styre, hvilke elementer der vises på Universal Portal.

De kan mærke ressourcer i PowerShell Universal for logisk at gruppere relaterede elementer sammen. Mærker kan også styre, hvilke ressourcer der vises på Universal Portal.

## Oprettelse af et mærke

For at oprette et mærke skal De klikke på **Manage > Tags** og derefter klikke på Create new Tag. Navnet er påkrævet, og alle andre egenskaber er valgfrie. Afkrydsningsfeltet "display in portal" angiver, om mærkede ressourcer vises i portalen.

## Visning af mærkede ressourcer

Når De har mærket ressourcer, kan De få vist mærkede ressourcer ved at gå til siden Tag og klikke på View Tagged Resources ud for det pågældende mærke.


---

# 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/powershell-universal/da/platform/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.