> 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/es/plataforma/tags.md).

# Etiquetas

Cree y gestione etiquetas en PowerShell Universal para agrupar lógicamente recursos relacionados y controlar qué elementos aparecen en el Universal Portal.

Puede etiquetar recursos en PowerShell Universal para agrupar lógicamente elementos relacionados. Las etiquetas también pueden controlar qué recursos aparecen en el Universal Portal.

## Crear una etiqueta

Para crear una etiqueta, haga clic en **Manage > Tags** y, a continuación, haga clic en Create new Tag. El nombre es obligatorio y el resto de propiedades son opcionales. La casilla de verificación Display in portal especifica si los recursos etiquetados aparecerán en el portal.

## Ver los recursos etiquetados

Después de etiquetar los recursos, puede verlos visitando la página Tag y haciendo clic en View Tagged Resources junto a la etiqueta en cuestión.


---

# 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/es/plataforma/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.