> For the complete documentation index, see [llms.txt](https://docs.santacruzsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.santacruzsoftware.com/bannersui/guides/brandkits.md).

# Brandkits

Create and use approved colors and fonts for consistent template branding.

Brandkits keep editing aligned with approved brand assets. They give teams a shared set of colors and fonts that can be attached to individual packages.

***

### Open brandkits

When brandkit management is enabled in the host configuration, designers can open the Brandkits dialog while editing a template. Select <kbd>Artboard Information</kbd> above the canvas, then select <kbd>Settings</kbd> in the Right Palette.

Select <kbd>Open Brandkits</kbd> to view existing brandkits or create a new one.

#### Attach an existing brandkit

1. Search for the brandkit.
2. Select the brandkit.
3. The brandkit is attached to the package.

{% hint style="info" %}
Each package can have only one attached brandkit.
{% endhint %}

#### Create a brandkit

1. Select <kbd>Create a Brandkit</kbd> from the Brandkit drop-down menu.
2. Enter a unique name and select <kbd>Create</kbd>. If that name already exists, enter a different name.
3. Add colors and fonts in the brandkit dialog.

Changes save automatically. Return to the template and add the brandkit to the artboard.

#### Manage colors and fonts

* **Add colors:** Add colors manually or from recent colors.
* **Update colors:** Name, edit, or delete colors. Color names must be unique.
* **Add fonts:** Upload brand fonts, choose existing account fonts, or add recent fonts.
* **Update fonts:** Name, edit, or delete fonts. Font names must be unique.

{% hint style="info" %}
When uploading a font, the editor requires confirmation that your organization owns the font and may use it online.
{% endhint %}

### Missing brandkits

The editor shows this warning when a package references a deleted brandkit.

<figure><img src="https://2414700618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtX06dIMKwlwZotca7AGa%2Fuploads%2FiW141Q2TQD9JazKYLsD9%2FScreenshot%202026-09-01%20093941.png?alt=media&amp;token=5d51fa60-9fde-47d1-842e-7444746ff424" alt=""><figcaption><p>Brandkit unavailable warning.</p></figcaption></figure>

Attach an available brandkit to continue using approved brand assets. This replaces the deleted brandkit for the package.


---

# 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.santacruzsoftware.com/bannersui/guides/brandkits.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.
