> 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-a-cms-in-a-docker-environment.md). # Applying a White label to a CMS in a docker environment {% 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
### Build and Download The build process can take up to 10 minutes in some circumstances. {% 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 ### Applying White Label Themes In a docker environment, the **theme name folder** should be copied to `/shared/cms/web/theme/custom/` (custom folder might need to be created manually) For example, if your theme name is ‘Xibo’, then in the downloaded archive you will find `theme/Xibo` folder, you will want to copy the ‘Xibo’ folder to the path specified above, the end path to your white label theme should be: `/shared/cms/web/theme/custom/Xibo` Where ‘Xibo’ is an obvious example, it will be your own theme name in the downloaded archive with White Label CMS theme. The **manual folder** from the archive, should be copied to `shared/cms/web/userscripts/`, meaning the full path will be `shared/cms/web/userscripts/manual` Once files are in place, log in to the CMS and navigate to the **Settings** page under the **Administration** section of the main CMSmenu. * On the **Configuration** tab, select your theme in the **CMS Theme** dropdown. * Go to the **General** tab, enter the following as the ‘Location of the Manual’ `userscripts/manual/en/` {% hint style="info" %} Please ensure you clear your browser cache (shift+F5 ) to see your custom theme applied to your CMS Instance. {% 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 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.xibosignage.com/kb/white-label-application/applying-a-white-label-to-a-cms-in-a-docker-environment.md?ask=&goal= ``` `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.