> For the complete documentation index, see [llms.txt](https://docs.xibosignage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xibosignage.com/kb/white-label-application/applying-a-white-label-to-the-cms.md).

# Applying a White label to the CMS

Applying a white label to your Xibo CMS allows for replacing the Xibo branding with your own corporate branding to include logos, splash screens and about text.

{% hint style="info" %}
A white label for the Xibo CMS does not change the license. You must retain the appropriate copyright notices and satisfy the terms of the AGPLv3 license: [GNU Affero General Public License version 3 | Open Source Initiative](https://opensource.org/licenses/AGPL-3.0)
{% endhint %}

### Remove Source and About links

A white label can be generated for the CMS which removes the **Source** and **About** links from the login page and also alters the text that appears within the **About** page throughout the CMS.

Removal of these items **does not** release a customer or end users from the terms of the [AGPLv3 license](https://opensource.org/licenses/AGPL-3.0) and therefore the license must be satisfied by the customer via alternative means.

Open a [Ticket](https://account.xibosignage.com/my-account/tickets?open=true) with our helpdesk via **My Account** to request a document template for the **Alternative Provision of License** to complete which will explain how the licence terms will be met with the absence of those items.

There are 3 main points to consider, this is not an exhaustive list and the AGPLv3 should be read and understood in full before submitting a request for these items to be removed:

* The source code or offer of source code **must be distributed** to your users by another means.
* The source code copyright and licence notifications **must not be modified** from their original appearance in the source code.
* The licence **must be distributed** to your users by another means.

{% hint style="info" %}
These options can only be enabled once we agree that the requirements are fully satisfied.
{% endhint %}

### Purchase and Configure

* Once purchased, click the **White Label** button from My Account
* Click to open the forms to configure by providing branding information and uploading resources

{% hint style="info" %}
If you have an accepted Alternative Provision of License, you have an additional License tab to remove the source and about links and provide 'About' text.
{% endhint %}

* Click the build button to queue

<figure><img src="https://3362620323-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FeoXfuIW0BLDTCFGqyP1i%2Fuploads%2F6JfdTc7QJVtmGnBJSaAe%2Fcms_white_label_queue_build.png?alt=media&amp;token=fc905ddb-7ec4-4809-aa39-8c038ddba79f" alt=""><figcaption></figcaption></figure>

### Build and Download

The build process can take up to 10 minutes in some circumstances.&#x20;

{% hint style="info" %}
If you see an Error status, check all fields have been completed with no missing information. Ensure that any uploaded images are in the specified formats.
{% endhint %}

Once the build is complete and ready for download, an email notification will be sent as per the 'Notify when built' field&#x20;

{% hint style="warning" %}
The `Application Name` cannot be changed after the first build.
{% endhint %}

### Applying White Label Themes

Users on a Plan can have their Theme automatically applied using the Theme selector when adding new CMS instances to the account.

To apply a theme to an existing CMS instance, open a [Ticket](https://account.xibosignage.com/my-account/tickets?open=true)

{% hint style="info" %}
Any changes made to the CSS after the white label has been applied will not automatically update to the CMS. Open a [Ticket](https://xibosignage.com/my-account/tickets?open=true) to request an update.
{% endhint %}


---

# 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.xibosignage.com/kb/white-label-application/applying-a-white-label-to-the-cms.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.