> 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/user-interface/ui-customization.md).

# UI customization

Customize the Remote Desktop Manager interface with ribbon or menu styles, light and dark themes, tab behavior, docking, dashboards, and vault types.

The UI customization section covers the visual and layout options available for tailoring Remote Desktop Manager to your preferences. This includes choosing between the [Ribbon, Menu bar, and Toolbar header styles](/rdm/user-interface/ui-customization/style.md), switching between light and dark [themes](/rdm/user-interface/ui-customization/theme.md), and adjusting [tab](/rdm/user-interface/ui-customization/tabs.md) appearance and behavior. More structural changes, such as [docking](/rdm/user-interface/ui-customization/docking.md) panels, customizing the [dashboard](/rdm/user-interface/ui-customization/dashboard-customization.md), and setting [vault content types](/rdm/user-interface/ui-customization/vault-content-types.md) to control which entry types are available per vault, are also configured here.


---

# 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/user-interface/ui-customization.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.
