> For the complete documentation index, see [llms.txt](https://docs.bluefletch.com/bluefletch-enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/bluefletch-launcher-for-windows/theming.md).

# Theming

The login screen, reauthentication screen, desktop, and taskbar follow your brand via the `theme` and `assets` configuration blocks (see [Technical Guide](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/bluefletch-launcher-for-windows/technical-guide)).

* **Logo** — Asset name to be shown on the login screens.
* **Wallpaper** — Asset name for the desktop background image.
* **Accent color** — A six-digit hex color applied to buttons, highlights, and hover states; contrast and hover shades are derived automatically.
* **Dark theme** — Renders the UI in dark mode. Choose dark or light mode that is best suited for the brightness and contrast of your background image.

### Assets <a href="#assets" id="assets"></a>

| Key         | Data Type                                    | Description                                                                                                             |
| ----------- | -------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| *(any key)* | **string** (mandatory block, arbitrary keys) | Either an `https://` URL, or an absolute local Windows path (e.g. `"C:\\ProgramData\\BlueFletch\\branding\\logo.png"`). |

### Full Example <a href="#full-example" id="full-example"></a>

```json
{
  "assets": {
    "bslogo": "https://ems-services-portal-demo.bluefletch.com/services/apiv1/files/downloadClientFile/85002129-f6b5-4cda-ae57-0bbb77162fa2?apikey=...",
    "bswallpaper": "C:\\ProgramData\\BlueFletch\\branding\\wallpaper.jpg"
  },
  "theme": {
    "enable": true,
    "logo": "assets:bslogo",
    "accentColor": "#004881",
    "wallpaperImage": "assets:bswallpaper",
    "darkTheme": false
  }
}
```

### When Changes Take Effect <a href="#when-changes-take-effect" id="when-changes-take-effect"></a>

A theme/asset change in `launcher.json` is picked up the next time the config is reloaded **and** the Launcher returns to the login screen (i.e. after a logout, or on app restart). It is not applied live to a screen that's already showing; in Open Zone (walk-up) mode, this happens automatically.

#### Disabling the Theme <a href="#disabling-the-theme" id="disabling-the-theme"></a>

Set `"enable": false` and omit (or ignore) the rest of the block. None of the other `theme` properties are read in this case - `logo`, `accentColor`, `wallpaperImage`, and `darkTheme` all resolve to built-in defaults.


---

# 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.bluefletch.com/bluefletch-enterprise/product-guides/bluefletch-launcher-for-windows/theming.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.