Skip to main content

Brand Identity & Legal Content Pages

Navigation Path: Sidebar → Experience Manager → Brand

TabLinkPermission
Brand Identity/org/experience?tab=brand:identityManage Org Level Global Settings for StoreFront
Brand Content/org/experience?tab=brand:contentBrowse & View Orbit Brand Page Content records (org Level)

The Brand section holds the two things every surface shares: your visual identity, and your company and legal pages.


1. Brand Identity (tab=brand:identity)​

One form, one card, five fields. Everything here is organization-wide and read by Storefront, Marketing, Resolve and Papers alike.

Figure 1 — The whole of Brand Identity. Changes are not live until you press Save.
A project can override this

The header on this screen says these values are shared by all customer portals — and they are, as a default. But a project's own Brand tab (Project → surface → Brand) wins for visitors on that project's storefront. The note at the foot of the card says it plainly: "a project's own branding wins for visitors on that project's storefront." Change something here and a project with its own branding will not move.

Figure 2 — The four pickers.
#FieldControlNotes
—Store nameText inputPlaceholder e.g. Agile Foods. Used in titles, text logos, footers and system emails.
1LogoImage pickerPick from Digital Assets or paste an external URL. Renders in the header of every customer portal.
2FaviconImage pickerThe browser-tab icon. ICO / PNG / SVG.
3Primary colorSwatch + hex inputPlaceholder #2563eb. Buttons, active nav, badges, CTAs.
4Secondary colorSwatch + hex inputPlaceholder #64748b. Secondary buttons, borders, subtle accents.

Both colour fields accept any CSS hex value — type it, or use the swatch for a visual pick.

Nothing on this screen auto-saves. Press Save (top right, or the bottom action bar on mobile); a toast confirms.


2. Brand Content (tab=brand:content)​

Orbit Brand Page Content (OBPC) holds your company and legal pages — About Us, Privacy Policy, Terms & Conditions, Return Policy — as versioned records that customer-facing pages can render.

Figure 3 — The Brand Content list.
Organization-wide scope

Every project shares the same brand content. There is no per-project override here. If one project genuinely needs different copy, create a separate record and put a project identifier in its title or slug — the screen says as much at the top.

Creating a record​

New brand page content opens a drawer with two fields:

FieldRequiredNotes
TitleYese.g. About Us
SlugNoDefaults from the title — e.g. about-us

Authoring, publishing and versions​

  • Draft vs published. Save as often as you like; nothing reaches visitors until you Publish.
  • ✨ AI generation. Describe the document in plain English and have the first draft written for you, then edit before publishing.
  • Delete removes a record — check nothing links to its slug first.