SendBeam

Brand kit

Set a workspace's colours, type, logo and icon once. New blocks and starters take them, every email can use them as merge tags, and blueprints carry them to the next site.

View as Markdown

Brand, in the left menu under This workspace, is where a workspace's look is defined once. Everything that makes email reads from it, so a designer setting up a client does not re-enter the same colours or re-upload the same logo in every template.

What the kit holds

  • Colours — primary (headers and buttons), secondary (headings), accent (links), background, surface (footers and quotes), text and muted.
  • Type — a heading and a body family from the email-safe list; each falls back to what the reader's client has.
  • Logo, logo on dark, icon — uploaded to the workspace's image hosting, or any https address.
  • Postal address and social links — for the footer the law asks for, and the row of icons under it.

A workspace that has not set a kit uses the built-in look, which is exactly what the builder always used.

Where it is used

  • The builder. A new block takes the brand's colours; a starter layout comes in re-coloured to the brand; every colour picker offers the palette as swatches. Emails made before the kit was set keep their own colours — the kit changes defaults, never existing work.
  • Merge tags, below, in any template, campaign, automation email or custom block.
  • Blueprints. Saving a workspace as a blueprint captures its kit; applying the blueprint to a new workspace sets it.

Merge tags

{{brand_name}}, {{brand_primary}}, {{brand_secondary}}, {{brand_accent}}, {{brand_background}}, {{brand_surface}}, {{brand_text}}, {{brand_muted}}, {{brand_logo_url}}, {{brand_logo_dark_url}}, {{brand_icon_url}}, {{brand_address}}, and {{brand_website_url}}, {{brand_instagram_url}} and the other social links. They resolve at send time, so a change on the Brand page reaches every email that uses them. A colour tag works anywhere a hex colour does — in a custom block's style, for example — and a URL tag in an src or href.

Agencies and several sites

One workspace is one site and one brand, so an agency sets a kit per client and blueprints carry it to the next client workspace. The API mirrors the page: GET and PUT /api/v1/brand with templates:read and templates:write.

Stuck, or found a gap? Ask in the community — questions, tips and every release note, with this page as the source of truth.