> 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/administration/system-settings/common.md).

# Common

Configure workspace-wide general behavior options in the Common section of Remote Desktop Manager System settings, including tab group color rules.

The ***Common*** section of the ***System settings*** contains workspace-wide general behavior options that apply broadly across users and sessions, such as system message settings and other shared configuration that doesn't fall under a specific security, user, or vault domain.

### Tab group color rules

The ***Tab group color rules*** page of the ***Common*** section assigns a color to the tab groups whose name matches a rule, for every user of the workspace. It holds the same ***Apply color to*** option and rule list as the ***Tab group color rules*** section of [***File*** – ***Settings*** – ***User interface*** – ***Tabs***](https://docs.devolutions.net/rdm/user-interface/ui-customization/tabs.md), where each option and rule field is described.

A rule defined here takes precedence over the rules that users define on their computer. When a tab group matches a rule of the workspace, the ***Apply color to*** value of the workspace applies. Otherwise, the local rules and ***Apply color to*** value of the user apply.

{% hint style="info" %}
Tab group color rules are not available in Devolutions Cloud workspaces.
{% endhint %}


---

# 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/administration/system-settings/common.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.
