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

# Personnalisation de l'interface

Personnalisez l'interface de Remote Desktop Manager avec les styles de ruban ou de menu, les thèmes clair et sombre, le comportement des onglets, l'ancrage, les tableaux de bord et les types de coffre

La section Personnalisation de l'interface couvre les options visuelles et de disposition offertes pour adapter Remote Desktop Manager à vos préférences. Cela comprend le choix entre les [styles d'interface Ruban et Barre de menus](/rdm/fr/user-interface/ui-customization/style.md), le passage entre les [thèmes](/rdm/fr/user-interface/ui-customization/theme.md) clair et sombre, ainsi que l'ajustement de l'apparence et du comportement des [onglets](/rdm/fr/user-interface/ui-customization/tabs.md). Des changements plus structurels, comme l'[ancrage](/rdm/fr/user-interface/ui-customization/docking.md) des panneaux, la personnalisation du [tableau de bord](/rdm/fr/user-interface/ui-customization/dashboard-customization.md) et la définition des [types de contenu de coffre](/rdm/fr/user-interface/ui-customization/vault-content-types.md) pour contrôler quels types d'entrées sont disponibles par coffre, se configurent également ici.


---

# 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/fr/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.