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

# Tab groups

Browse active tab groups in a docked window with the Tab groups feature in Remote Desktop Manager to organize and manage multiple open session tabs.

The ***Tab groups*** feature opens a docked window showing a tree view of the various tab groups. It is possible to select multiple tabs at once by <kbd>Shift</kbd>-clicking or all of them with the <kbd>Ctrl</kbd>+<kbd>A</kbd> shortcut. Right-clicking on one or more tabs shows more options.

The other tab groups will only appear if a session that is part of a tab group (other than the ***All*** tab) is active.

Although it is docked by default, the ***Tab groups*** pane can be windowed, dragged, and docked anywhere within Remote Desktop Manager.

To learn how to create a tab group, refer to [***Tab group bar***](/rdm/ribbon-menu-bar/view/tab-groups/tab-group-bar.md).

#### See also

* [Devolutions Academy – Manage tabs using tab groups](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/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.
