> For the complete documentation index, see [llms.txt](https://docs.akenza.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akenza.io/device-management/managing-an-organization/general-settings/white-labeling.md).

# White Labeling

Present akenza under your own name, colors, and logo.

**White labeling** replaces akenza's own branding with yours, so that the people using the platform, and the notifications it sends them, carry your name rather than akenza's. It applies to the whole organization and everything underneath it.

This matters most when the people using akenza are not your colleagues. A facility manager at a customer site, or a tenant opening a shared dashboard, sees your product rather than a platform they have no relationship with.

{% hint style="info" %}
White labeling is available on **Expert plans**. See [akenza.io/pricing](https://akenza.io/pricing) for what each tier includes.
{% endhint %}

## Turning it on

Open **White label settings** on the [General settings](/device-management/managing-an-organization/general-settings.md) page and enable **White label your Organization**. The settings below become available, and *Save* applies them.

## What you can change

<table><thead><tr><th width="230">Setting</th><th>What it affects</th></tr></thead><tbody><tr><td><strong>Application name</strong></td><td>The product name shown throughout the application in place of "akenza".</td></tr><tr><td><strong>SMS sender name</strong></td><td>The sender that recipients see on <a href="/device-management/your-data-flow/connectors/notifications/sms.md">SMS notifications</a>.</td></tr><tr><td><strong>Primary color</strong></td><td>The main accent color of the interface, given as a hex value such as <code>#1890ff</code>.</td></tr><tr><td><strong>Success, warning, and error colors</strong></td><td>The status colors used for positive, cautionary, and error states.</td></tr><tr><td><strong>Application logo</strong></td><td>Either an uploaded <strong>image</strong> or a <strong>monogram</strong> generated from your application name.</td></tr><tr><td><strong>Wide logo</strong></td><td>An optional second logo for the places where a wide mark fits better than a compact one.</td></tr></tbody></table>

### Logos

Choose **Image** if you have a compact company logo, or **Monogram** to derive a mark from the application name instead. Once an image is uploaded you can replace or delete it. Enabling **Upload additional wide logo** lets you supply a wide variant alongside the compact one.

{% hint style="warning" %}
Pick status colors that stay distinguishable from one another. Success, warning, and error carry meaning across dashboards and device states, so a palette where they read as similar shades makes the interface harder to scan, however well it matches your brand.
{% endhint %}

## Where it shows

White labeling reaches the application interface, the logos and colors in it, notifications your rules send, and dashboards shared through a [public link](/dashboard-builder/managing-dashboards/public-links.md), including [signage screens](/dashboard-builder/signage-screens.md) and [embedded dashboards](/dashboard-builder/embedding-dashboards.md).


---

# 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://docs.akenza.io/device-management/managing-an-organization/general-settings/white-labeling.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.