> 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/fr/plateforme/tags.md).

# Étiquettes

Créez et gérez des étiquettes dans PowerShell Universal pour regrouper logiquement les ressources connexes et contrôler quels éléments apparaissent dans le Universal Portal.

Vous pouvez étiqueter des ressources dans PowerShell Universal pour regrouper logiquement les éléments connexes. Les étiquettes peuvent aussi contrôler quelles ressources apparaissent dans le Universal Portal.

## Créer une étiquette

Pour créer une étiquette, cliquez sur **Manage > Tags**, puis cliquez sur Create new Tag. Le nom est obligatoire et toutes les autres propriétés sont facultatives. La case à cocher display in portal précise si les ressources étiquetées apparaîtront dans le portail.

## Afficher les ressources étiquetées

Après avoir étiqueté des ressources, vous pouvez afficher les ressources étiquetées en visitant la page Tag et en cliquant sur View Tagged Resources à côté de l'étiquette en question.


---

# 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/fr/plateforme/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.