> 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-community-build/user-guide/managing-your-account/appearance.md).

# Appearance

You can select the theme of the SonarQube Community Build interface to match your own preferences.

The interface theme defines the appearance of windows, dialog boxes, buttons, and other visual elements of the user interface.

The theme is a personal preference. Your selection applies to your own account only and does not affect other users of the instance.

New accounts use the *Sync with system* theme by default. Accounts that existed before theme selection was introduced keep the light theme until you select a different option.

You can select any of the following three options:

* **Sync with system**: SonarQube Community Build detects the current system settings and uses the 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.

To select a theme:

1. Select your account menu in the top right corner of the SonarQube Community Build interface.
2. In the menu, select **My Account**.
3. Select the **Appearance** tab.
4. Select the theme you want to use.


---

# 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.sonarsource.com/sonarqube-community-build/user-guide/managing-your-account/appearance.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.