> For the complete documentation index, see [llms.txt](https://teos-docs.coreledger.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://teos-docs.coreledger.net/white-label-mobile-app/admin-user-guide/app-configuration/branding-management.md).

# Branding management

The WLA look and feel can be customized to a specific degree. All options can be set in the corresponding config file (The config file is stored on our Azure blob in the root of the folder **trading-app-configs** and called *ui\_config.v1.json*).

Every change in this file is reflected in the WLA immediately after restarting the app or after manually updating the configuration in the app. To do the manual update go to settings, select “About the app” and then click “Update configs”.

## Application colors

The upper part of the config file is about the colors of the app, which are expressed as HEX colors

```
"colors": {
"background": "#f5f5f5",
"backgroundMainColor": "#e6e6e6",
"backgroundSecondColor": "#e6e6e6",
"textFields": "#ffffff",
"accentColor": "#988e9e",
"textMainColor": "#1a1021",
"textSecondColor": "#755c87",
"btnTextColor": "#34104d",
"error": "#b50514",
"warning": "#f27f05",
"success": "#016113",
"dividers": "#0a46bf",
"menu": "#bdb8c2"
},
```

## In app logo

The following part is about the logo you could configure for the app. The logo needs to be stored in the blob and the path to it as well as the file name needs to be inserted in the config file *ui\_config.v1.json*. We recommend to use folder **trading-app-configs/logos** to store all necessary logos.

The following refers to the logo loading screen and the logo in the settings:

```
"img": {
"logo": "logos/coreledger@2x.png",
"menu_logo": "logos/coreledger@2x.png",
},
```


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://teos-docs.coreledger.net/white-label-mobile-app/admin-user-guide/app-configuration/branding-management.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.