What it does

A brand profile bundles the things that make an email look and sound like it came from a particular brand: the senders it can go out from, the social links in the footer, and the fonts and colours applied to draft content. Themes handle styling inside a single email; templates give a whole email its starting layout.

Key facts

• Brand profiles live under Settings > Customer engagement > Brand profiles. You create them with +New and they carry a name and description plus three tabs that matter.
• The Senders tab holds one or more senders, each with From email, From name and Reply-to email, and a Default sender toggle. One profile can carry several senders — regional, departmental, whatever the brand needs.
• The Social links tab is an editable table, so you can add platforms beyond the ones shipped. Those values are then available through the personalisation window, which is how you wire a social icon's URL to the profile rather than hard-coding it per email.
• The Theme tab sets brand fonts and colours, and those apply automatically to draft content using that profile.
• Authors pick the profile from the Brand profile dropdown at the top right of the email designer. Selecting it drops that profile's default sender into Send settings, and they can swap to another sender from the same profile using the lookup in the Sender box.
• Leaving the sender box empty lets an author type a one-off sender that bypasses the profile entirely. Worth knowing, because it also bypasses your governance.
• The brand profile table is a normal Dataverse table and is extensible — custom fields are fair game if the client's branding needs more than the shipped set.
• You can run multiple profiles, including one per business unit, which is the usual pattern for multi-brand organisations.
• Themes are per-email, reached from the brush icon in the designer's right pane. A theme styles every element of the same type at once — change the button style and all buttons move. Element-level properties override the theme where they're explicitly set.
• Templates are a starting layout, one per email, copied at creation. Template edits never flow into emails already created from them.

When to use / skip

If the client has one brand, one sending domain and one marketing team, a single brand profile plus two or three templates is the whole job and you should not build more. The feature earns its cost the moment there are genuinely separate brands, separate business units, or a franchise/regional structure where the wrong footer on the wrong email is a real problem.

Themes are worth setting properly on every project — it's ten minutes and it stops authors hand-styling every button slightly differently. Templates are worth a small number, built well. Long template libraries are a maintenance liability because nothing propagates.

Configuration decisions

• How many profiles, and whether the split is by brand, by business unit, or by region. Business unit alignment is the harder one to change later, because it drags ownership and visibility with it.
• Which senders belong to which profile, and which is the default. This interacts directly with domain authentication — a sender on an unauthenticated domain will get rewritten or blocked at go-live.
• Whether social links are managed centrally through the profile or left to templates. Centralise them; the alternative is chasing a changed handle through forty emails.
• Where the styling authority sits: brand profile theme, email theme, or element-level properties. Pick a level and hold to it, because the override order gets confusing fast.
• How many templates, and whether the brand's footer and header live in templates or in section content blocks. Blocks update; templates don't.
• Whether authors are permitted to enter one-off senders, and if not, how you police it.

Gotchas

• Brand profile updates don't reach published emails. The documented fix is to open the email, switch to a different brand profile, switch back, and republish — which means a brand refresh is a manual pass over every live email.
• Template changes don't propagate either. Two non-propagating mechanisms in the same feature area catches people out constantly; content blocks are the only thing that updates in place, and only dynamic ones at that.
• Changing an email's template after content exists discards the body. Authors treat the template dropdown as a preview control and lose work.
• Element properties beat the theme. An author who once set a button colour by hand won't see the rebrand land on that button, and it'll be the one button nobody checks.
• Profiles scoped to a business unit are only usable inside it, which is fine until someone asks why the central team can't send on behalf of a subsidiary.
• A default sender in the profile doesn't guarantee the email sends from it — the default sending domain and the error check on go-live can still rewrite or block the From address.

Consultant notes

• Build the brand profile before anyone writes an email. Retrofitting it is a per-email manual job and the client will assume you did it wrong.
• Demo the rebrand scenario honestly: show that the profile updates drafts automatically and that live emails need a republish. Better to have that conversation in design than in a change request.
• Tie the brand profile senders to the authenticated domains explicitly, on one page, and get sign-off. It's the single most common go-live blocker in this area.
• Push back on a template per campaign. Argue for a small template set plus section content blocks for the repeating furniture.
• Before go-live, check every live email actually resolves to the intended brand profile — including any built during the trial or the proof of concept, which almost never do.

---

Worth another look if brand profile updates ever start propagating to published emails, or if theme handling changes in the designer.