How to Set Up and Use Brand Kit
This guide explains how to create and configure a brand in Brand Kit, and how editors use brand assets — logos, colors, fonts, and typography presets — when building microapps.
Overview
Brand Kit gives Library Administrators a central place to define brand standards — logos, colors, fonts, and typography — and make those assets automatically available to editors in the Builder. When a brand is active for a microapp, editors see brand colors in the color picker, brand fonts in the font selector, brand logos in the asset picker, and typography presets ready to apply in one click.
Brand Kit is a Builder 2.0 feature.
What Brand Kit Includes
|
Feature |
What it does |
|
Brand colors |
Brand palettes appear as the primary color palette in the Builder color picker |
|
Brand fonts |
Uploaded brand fonts appear as a distinct group at the top of the font dropdown |
|
Typography presets |
Heading, Body, Caption, and custom presets apply the correct font, weight, and size in one click |
|
Brand logos |
Multiple logo variants (primary, secondary, icon, dark-mode) available directly in the asset picker |
|
Default styles on tile creation |
New tiles are created with brand colors and fonts already applied when a brand is active |
|
Brand import from URL |
Enter a company URL to automatically retrieve publicly available logos, colors, and fonts |
|
Library default brand |
Administrators set a default brand — all new microapps in the library use it automatically |
|
Brand selector at creation |
Creators can choose a different brand or start without one when creating a new microapp |
Setting Up a Brand (Administrators)Step 1 — Create the Brand
1. Navigate to Library Settings > Brand Kit.
2. Click Create Brand.
3. Enter the brand name.
4. To auto-import brand assets, enter the company website URL. Tiled retrieves publicly available logos, colors, and fonts automatically.
5. Review the imported assets and add any official brand files that weren't retrieved automatically.
|
Note: Brand import is powered by publicly available brand data. The completeness of what's retrieved varies by company — always review imported assets and supplement with your official brand files before publishing. |
Step 2 — Configure Typography Presets
In the brand record, set up typography presets: Heading, Body, Caption, and any custom presets your team needs.
For each preset, configure the font family, weight, and size.
Step 3 — Assign and Set as Default
Assign the brand to one or more libraries.
Optionally, set this brand as the library default — all new microapps in the library will use it automatically.
Using Brand Assets in the Builder (Editors)
When a brand is active for a microapp, brand assets are available throughout the Builder without any additional setup:
1. Create a new microapp. If the library has a default brand, it's applied automatically. To use a different brand, select it from the brand selector in the creation modal.
2. Add a text tile. Brand typography presets appear at the top of the font selector — select a preset to apply the brand font, weight, and size in one step.
3. Open the color picker. Brand colors appear as the primary palette.
4. Open the asset picker. Brand logo variants are listed and ready to insert.
New tiles you add are created with brand colors and fonts already applied.
Changing a Microapp's Brand After Creation
If a microapp was created without a brand (or with a different brand than intended), you can assign or change its brand at any time from the microapp's Settings.
1. Open the microapp and go to Settings.
2. Locate the Brand setting — it will show None or the currently assigned brand.
3. Select the brand you want to apply.
4. Save your changes.
|
Note: Changing a microapp's brand applies going forward. Any new tiles you add from that point on will automatically use the assigned brand's colors and fonts, the same as if the brand had been active from the start. Tiles that already existed before the brand was assigned are not retroactively restyled. |
Roles & Permissions
|
Role |
What they can do |
|
Library Administrator |
Create, configure, and manage brands; assign brands to libraries; set library default brands; configure typography presets |
|
Editor |
Select a brand when creating a microapp, or change it later from microapp Settings; use brand typography presets, colors, and logos in the Builder; cannot create or modify brand records |
|
Viewer |
Sees brand-styled microapps in the Viewer; no brand management access |
Common Questions
Does Brand Kit work with Builder 1.0 microapps?
No — Brand Kit is scoped to Builder 2.0. Builder 1.0 microapps do not inherit brand colors or styles from Brand Kit configuration.
Can a library have more than one brand?
Yes — you can create multiple brand records and assign them to libraries. The library default determines which brand is applied automatically to new microapps, but editors can select a different brand at creation time.
What happens if I create a microapp without selecting a brand?
If the library has a default brand, it's applied automatically. If no default is set, the microapp starts without a brand — editors can apply brand assets manually from the color picker, font selector, and asset picker. You can also assign a brand at any time afterward from the microapp's Settings (see “Changing a Microapp's Brand After Creation” above) — once assigned, any new tiles you add from that point on will automatically use the brand's colors and fonts.
Can editors modify brand records?
No — brand records can only be created and modified by Library Administrators. Editors can use brand assets but cannot change brand configuration.
The brand import didn't retrieve all our assets — what should I do?
Brand import retrieves publicly available data and may not capture all assets for every brand. Review the imported results and manually upload any logos, fonts, or colors that weren't retrieved. Always verify imported assets against your official brand guidelines before use.
Can I change the library default brand after microapps have been created?
Yes — changing the library default affects new microapps going forward. Existing microapps retain the brand that was applied when they were created.