> For the complete documentation index, see [llms.txt](https://developers.make.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.make.com/white-label-documentation/customize-your-instance/rebrand-your-instance.md).

# Rebrand your instance

The system settings page lets you customize the appearance, name, support, and available features of your instance. To access and edit these settings, go to **Administration > System Settings** and find the corresponding field.

### Name and appearance

The following fields let you customize the name and appearance of your instance.

<table data-header-hidden><thead><tr><th width="267"></th><th></th></tr></thead><tbody><tr><td><strong>Brand title</strong></td><td>The name that appears in the browser tab and in email communication to your end user.</td></tr><tr><td><strong>Brand theme</strong></td><td>Select one of the available colors. This color applies to the login page, public side navigation bar, and other UI features.</td></tr><tr><td><strong>Brand favicon</strong></td><td>Upload or drag and drop a <code>.ico</code> file to appear in browser tabs when your users have it open.</td></tr><tr><td><strong>Brand logo (for dark background)</strong></td><td><p>Upload or drag and drop a .png file to appear against dark backgrounds.</p><p>Recommended size is 512 x 512 px with a square image.</p><p>The logo you upload here appears on the login screen.</p></td></tr><tr><td><strong>Brand logo (for light background)</strong></td><td><p>Upload or drag and drop a .png file to appear against light backgrounds.</p><p>Recommended size is 512 x 512 px with a square image.</p></td></tr></tbody></table>

{% hint style="warning" %}
The name and appearance settings do not impact the administration interface. You need to click Leave administration to confirm the changes. Recent changes may take several minutes to appear in your UI.
{% endhint %}

### Support root URLs and emails

Support root URLs provide a base URL for UI links to support documentation and tickets.

<table data-header-hidden><thead><tr><th width="272"></th><th></th></tr></thead><tbody><tr><td><strong>Support email</strong></td><td>The name and appearance settings do not impact the administration interface. You need to click <strong>Leave administration</strong> to confirm the changes. Recent changes may take several minutes to appear in your UI.</td></tr><tr><td><strong>SDK App Help Root</strong></td><td>This URL only impacts the custom app editor and is not necessary if the Apps Platform is disabled. Enter the URL for documentation on creating custom apps.</td></tr><tr><td><strong>Help Center Root</strong></td><td>This URL provides a base URL for in-product user support. Your users encounter this when they click on the <strong>?</strong> when editing module settings.</td></tr><tr><td><strong>Open Ticket Root</strong></td><td>This URL links to your customer support ticketing system. When users click on Contact Support, a new tab opens with the URL you enter in this field.</td></tr></tbody></table>


---

# 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://developers.make.com/white-label-documentation/customize-your-instance/rebrand-your-instance.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.