> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-cloud/managing-your-account/user-interface.md).

# Customizing your UI

You can customize the theme of the SonarQube Cloud UI to match your own preferences.

The SonarQube Cloud interface theme defines the appearance of windows, dialog boxes, buttons, and other visual elements of the user interface. It is not the same as the color scheme (that covers colors, fonts, etc).

When you first log into SonarQube Cloud, the default setting is the *Sync with system* theme. For existing users, the light theme is selected as the default option, but in both cases, you can select any of the three options:

* **Sync with system**: SonarQube Cloud detects the current system settings and uses the default dark or light theme accordingly.
* **Light theme**: The traditional light theme.
* **Dark theme**: A darkened appearance in which the UI text and content stand out while windows and controls appear to recede into the background.

If you change your mind later, you can change your selection by going to **User** > **My Account** > **Appearance** and switching to the theme of your choice.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-cloud/managing-your-account/user-interface.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 `build a script that syncs our docs to a CMS` 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.