> 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/rdm/es/ribbon-menu-bar/view/tab-groups.md).

# Grupos de pestañas

Explore los grupos de pestañas activos en una ventana anclada con la función Grupos de pestañas de Remote Desktop Manager para organizar y gestionar varias pestañas de sesión abiertas.

La función ***Grupos de pestañas*** abre una ventana anclada que muestra una vista de árbol de los distintos grupos de pestañas. Es posible seleccionar varias pestañas a la vez haciendo clic con <kbd>Shift</kbd> o todas ellas con el atajo <kbd>Ctrl</kbd>+<kbd>A</kbd>. Al hacer clic con el botón derecho en una o varias pestañas se muestran más opciones.

Los demás grupos de pestañas solo aparecerán si está activa una sesión que forma parte de un grupo de pestañas (distinto de la pestaña ***Todos***).

Aunque está anclado de forma predeterminada, el panel ***Grupos de pestañas*** se puede convertir en ventana, arrastrar y anclar en cualquier lugar dentro de Remote Desktop Manager.

Para saber cómo crear un grupo de pestañas, consulte [***Barra de grupos de pestañas***](https://docs.devolutions.net/rdm/es/ribbon-menu-bar/view/tab-groups/tab-group-bar.md).

#### Véase también

* [Devolutions Academy – Gestionar pestañas mediante grupos de pestañas](https://academy.devolutions.net/student/page/2641980-manage-tabs-using-tab-groups?sid=5e1ad270-9ecb-41cb-9d9d-6de6d80f4a3b\&sid_i=3)


---

# 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/rdm/es/ribbon-menu-bar/view/tab-groups.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.
