Brand file (Brand Hub)
The brand is the single place where its visual identity (the kits), legal data, channels, campaigns, field reps and products live. Menu: Brands (top level, right below Campaigns).
Brands permission · Edition: all. The tabs of the brand file are shown according to your permissions (see Permissions).
To see where the brand fits (account → client → brand → campaign): Accounts, clients and brands. Client data is managed in Clients and brands.
Create a brand
- In Brands click New (you need the Creating Brand permission). A three-step wizard opens.
- Name and client: the client is required (it is the brand's legal promoter). If it doesn't exist, create it right there with New client › Create client. Under the name you'll see the Public URL (the slug), generated from the name.
- Colours: upload a logo and the wizard suggests a palette extracted from it, or pick colours by hand. It warns when the text on the accent colour fails the WCAG AA contrast (4.5:1). You can also Use the tenant kit.
- Legal: optional legal data for the brand.
- Click Create brand. Steps 2 and 3 can be skipped with Skip this step, or with Create brand now.
Once created, the brand file has these tabs:
| Tab | What it is for |
|---|---|
| Summary | Overview and brand metrics |
| Data & legal | Name, slug, website, language and legal texts |
| Identity | The brand's visual kits |
| Channels | Communication channels pinned to the brand |
| Campaigns & landings | The brand's campaigns and landings |
| Field reps | Assigned field reps |
| Products | The brand's products |
| Settings | Activate/deactivate, duplicate, transfer and delete |
Visual kits
A kit gathers the visual identity: colours (Primary, Secondary, Accent, Background, Text, plus the Win / Lose / Pending status colours), Heading font, Body font, Corner radius, Button style (Solid, Outline, Pill), logo, monochrome logo, favicon and custom CSS. The editor shows a preview and an AA contrast check.
- A brand can have several kits (for example, one per season). Manage them in Identity › Brand kits: New kit, Duplicate, Set as default.
- The brand's default kit is the one inherited by its campaigns and landings that don't choose another.
- If the brand has no kit of its own, the tab says it uses the tenant default kit. Use the tenant kit puts it back in that state.
- General kits (account-wide, with no brand) are under Brand & content › General brand kits. One of them is the account default.
Kits are not shared between brands
A brand kit can only be used with that brand. To reuse another brand's kit, duplicate it: Duplicate or Duplicate from a general kit…. The copy is named "name (copy)" and evolves on its own. Assigning another brand's kit to a campaign or landing is rejected with the error "The kit … does not belong to the brand …".
Deleting a kit
A kit in use cannot be deleted; the message says who uses it (default brand, campaigns, landings, member portal). The Used by column on the tab shows it beforehand. Unlink first, then delete.
How the applied kit is resolved
The closest explicit choice always wins; if there is none, it is inherited from the next level.
A campaign's landing: landing → campaign → brand → tenant.
| Landing (⋯ › Brand kit) | Campaign (Brand kit) | Brand default | Tenant default | Applied kit |
|---|---|---|---|---|
| Kit A | — | — | Kit T | A (chosen on the landing) |
| — | Kit B | Kit M | Kit T | B (chosen on the campaign) |
| — | — | Kit M | Kit T | M (brand default) |
| — | — | — | Kit T | T (tenant default) |
| — | — | — | — | No kit: default look |
Other contexts:
- Program landing and member portal: page → portal kit → tenant default. They only accept general kits.
- Account landing: page → tenant default.
- Field rep portal (
/rep) and invitations: the brand's default kit, or the tenant's if it has none.
Useful rules:
- On the campaign, the Brand kit selector offers the Brand default, that brand's kits and the General kits. To go back to the default, clear the choice.
- If you change the brand of a campaign that had a kit from the previous brand, the system rejects it; the dialog offers Use default.
- The tenant default kit is always an explicit decision: creating your first general kit does not make it the default.
- If a link points to a kit that is no longer valid for that scope, it is ignored and the next level is inherited.
- A campaign's default landing (the one not designed in the editor) and the member portal do not change look when you create brand kits. For the default landing to use the campaign's kit, you must enable it explicitly on the campaign.
- Changes can take up to about 10 minutes to show because of the resolution cache.
Recipe: seasonal kit
- In Identity, create a kit (or duplicate the current one) with the season's colours.
- On the campaign, choose it in Brand kit.
- When the season ends, clear the choice on the campaign: it goes back to the brand default.
More about the selector inside the editor: Landing builder › Brand kits.
Slug and public URL
In Data & legal › Slug you set the brand's public identifier.
- Lowercase letters, digits and single hyphens only (no leading or trailing hyphen), up to 64 characters. It is lowercased on save.
- It is unique per account among non-deleted brands. A duplicate is rejected.
- It is optional: the wizard suggests one from the name.
The brand publishes a page with its active campaigns at the public endpoint GET /api/public/landing/b/{slug}, which returns the brand, its kit and its campaigns (with each one's slug). If the domain it is queried from belongs to an account, only that account's brands are served; on a shared domain the oldest non-deleted brand with that slug wins. A deactivated or unknown brand answers 404; an active brand with no active campaigns answers 404 with the code brand_has_no_active_campaigns.
Today the application does not include a web screen for this URL: the endpoint serves data for integrations and for whoever builds the page. Campaigns keep being published at their own URL: Campaign landing.
Inherited legal texts
The brand has no tax data of its own: its legal promoter is the client. In Data & legal:
- Legal (promoter) (read-only): the client's legal name, tax ID, address and contact. The Edit in the client link opens the client (requires the Clients permission).
- Brand legal (editable): Privacy URL, Terms URL, DPO email, Support email and Legal contact.
Each brand field is an optional override:
| Brand field | What is used |
|---|---|
| Empty | The client's (the field shows "Inherited from the client: …") |
| Filled | The brand's |
To override, type your own value and save. To inherit again, click Use the client's (or empty the field) and save. URLs must be absolute https:// (max 500 characters); others are rejected.
For a campaign's texts, the order is: the campaign's participation policy → brand → client. A campaign without a brand only uses its policy URLs. The Legal footer preview shows the result, and Copy placeholders copies the markers for templates.
Change the value on the client if it should apply to all its brands; override it on the brand only when it differs.
Brand settings
In Settings:
- Deactivate brand: it stops appearing when creating campaigns.
- Duplicate brand: copies legal data, kits (new, not shared) and channel pins. It does not copy campaigns, slug or the WhatsApp link.
- Transfer to another client: the legal promoter and inherited data become those of the new client.
- Delete brand: not possible while it has non-archived campaigns. Deleting also removes its kits and channel pins.
Permissions
| Action | Permission |
|---|---|
| View brands, Summary and Settings tabs | Pages.Loyalty.Brands |
| Create / edit / delete | Pages.Loyalty.Brands.Create · .Edit · .Delete |
| Data & legal tab | Pages.Loyalty.Brands.Edit |
| Identity tab (brand kits) | Pages.Loyalty.Brands.ManageKit |
| Channels, Campaigns, Field reps, Products tabs | Each area's permission |
| General kits | Pages.Loyalty.WhiteLabel |
A brand's kits can be edited with the white-label permission or with Brands.ManageKit.