> 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/theming.md).

# Theming

Theming enables administrators to customize the visual appearance of the Launcher interface across workforce devices. It establishes a cohesive user experience by applying company logos, color schemes, and site-specific designs that align with organizational branding.

**Site-Specific Theming:** Customizes the device interface with unique logos, colors, and wallpapers specific to one store or site.

**Configure Theme:** Supports the customization of the Launcher's visual appearance to match your organization's branding.

**Custom Field Display:** Extracts values from external files using regular expressions to display device-specific information on the home screen.

**Icon Shape:** Defines the visual shape of application icons displayed within the main workspace.

**Screen Saver:** Displays a rotating playlist of media assets during device inactivity to provide a dynamic visual experience.

<br>


---

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