> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/start-here/org-settings/brands.md).

# Brands

Create, update, apply, and remove tenant brand kits.

Brands lets enterprise customers customize Qore Workbench and deployed apps to match brand guidelines.

A brand kit stores your tenant’s platform name, logos, and color scheme. White-labeling lets you deliver Qore under your own brand across deployments.

Qore uses the applied kit across branded platform surfaces.

| Topic        | Details                                                                               |
| ------------ | ------------------------------------------------------------------------------------- |
| Access       | Super admins manage brands at **Super Admin Settings → Brands**.                      |
| Brand kit    | Stores a brand name, platform name, logo assets, colors, and advanced theme settings. |
| Active brand | One brand is applied at a time.                                                       |
| Main actions | Create, update, apply, or delete brand kits.                                          |

## Overview

The applied brand represents your tenant in Console and user-facing flows. It also appears in transactional emails, generated documents, and exports.

A tenant can store several brand kits. Only the applied kit is visible to users.

### Key concepts

| Concept       | Meaning                                                     |
| ------------- | ----------------------------------------------------------- |
| Brand name    | An internal label for identifying a kit in the list.        |
| Platform name | The name shown on branded user-facing surfaces.             |
| Brand assets  | The **Large logo**, **Small logo**, and **Favicon** images. |
| Applied brand | The kit currently used across every branded surface.        |

## Manage brands

The Brands list shows every brand kit as a card. The **Create custom Brand** card starts a new kit.

Each existing card shows its thumbnail, **Brand Name**, and **Last updated on** date. Select a card to update it.

Use **Apply** to activate a kit. Use the **⋮** menu to delete one.

### Use a theme template

Qore includes theme templates. Select a template, then select **Apply** to use it.

### Create a brand

Create a kit to prepare a new tenant identity. It isn't applied automatically.

{% stepper %}
{% step %}

### Start a brand kit

Select **Create custom Brand**. The **Brand Kit** view opens with a live preview.
{% endstep %}

{% step %}

### Add brand details

Enter a **Brand Name** and **Platform Name**. The brand name stays internal.
{% endstep %}

{% step %}

### Add assets and colors

Upload a **Large logo**, **Small logo**, and **Favicon**. Set **Primary Brand Color** and **Secondary Brand Color**.

Use **Advanced Customization** for additional theme controls. The preview updates as you edit.
{% endstep %}

{% step %}

### Save the brand

Select **Create Brand**. Qore adds the kit to the Brands list.
{% endstep %}
{% endstepper %}

### Update a brand

Select a brand card to open **Update Brand Kit**. Change its details, then select **Save**.

Saving changes doesn't apply an inactive kit. Changes to the applied kit appear immediately.

### Apply a brand

Select **Apply** on a card to activate its brand kit. Qore replaces the previous applied kit everywhere.

The change updates Console and user-facing surfaces. Newly generated documents and exports use the active kit.

### Delete a brand

Open the card's **⋮** menu and select **Delete**. Confirm the removal.

{% hint style="danger" %}
Deletion is permanent. Apply a different brand before removing the active kit.
{% endhint %}

### Related

<table data-view="cards"><thead><tr><th>Title</th><th>Description</th><th data-card-target data-type="content-ref">Target</th></tr></thead><tbody><tr><td>Accounts</td><td>Manage tenant accounts, credit limits, and usage alerts.</td><td><a href="/start-here/org-settings/accounts.md">Accounts</a></td></tr><tr><td>Cost Management</td><td>Track credit consumption and control spending.</td><td><a href="/control-center/cost-control.md">Cost Control</a></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 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.uptiq.ai/start-here/org-settings/brands.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.