Skip to main content
Brand identity settings cover the atlas-wide settings that govern the brand record itself: the brand’s name, the author, milestone history, exports, retention, and the operational metadata of the brand. Open Settings → Brand identity.

Atlas name and basic metadata

  • Atlas name. The display name of the atlas, used in the sidebar header, on Guest Passes, in exports. Editable by the brand owner.
  • Brand identifier. The brand’s short identifier for cross-tenant references and CMS integration. Set at atlas creation; editable but rarely changed.
  • Brand description. A one-sentence description used as default copy on Guest Passes and exports. Editable.
  • Created. The date the atlas was created. Not editable.
  • Region. The primary jurisdiction for the brand. Used for compliance defaults (accessibility target, photography location release norms). Editable.

The brand author

The single accountable author of the brand record. By default, the current brand owner.
  • Current author. Name, email, role.
  • Transfer authorship. Initiates an authorship transfer. See Team and seats for the flow.
  • Authorship history. A list of past authors, with the date of each transfer.
The author is a separate concept from the brand owner role in the rare case the brand owner is a corporate entity rather than a person; in that case the named author records the human accountable for the work.

Milestone versions

Milestones are marked points in the brand record’s history that the team can refer to. They serve as stable references for printed deliverables, contracts, and anniversaries. The settings page shows:
  • Active milestones. A list of current milestones with their date and a short description.
  • Publish a new milestone. Captures the current state of the brand record as a milestone. You name it, describe it, and confirm. The milestone is immutable from that moment.
  • Compare milestones. Side-by-side diff between two milestones, useful for evolution reviews.
A common milestone cadence is one per year (annual brand snapshot), plus per evolution event (a wordmark refresh, a typeface change, a major partnership).

Brand record history

  • Retention. How long the brand record’s history is kept at full detail. Set by tier; cannot be reduced below the tier minimum.
  • Audit log. Every change to the brand record, with who, when, and what. Searchable, filterable, exportable.
  • Restore from history. Roll back a section or Horizon to a past state. Available only to the brand owner; recorded as an action in itself.

Export the brand record

  • PDF milestone. A printable PDF of the current brand record as a single document. Used for handover and contractual deliverables.
  • MDX bundle. A ZIP file of MDX files per section and Horizon, with a manifest. Reversible: a future atlas can be populated from these files.
  • JSON record. A structured JSON representation of the brand record, with attribution and change history.
See Cancelling and exporting for the export details.

AI configuration summary

A summary of which AI features are enabled. The full configuration is on the dedicated AI pages:
  • Henry. Enabled or disabled. Provider in use (OpenAI or Gemini). Key status.
  • Oswald. Enabled or disabled (Guardian only).
Edit from Settings → AI.

Domain and white-labelling

For Guardian customers using custom domains and white-label branding. See Domain and white-labelling.

Compliance settings

  • Accessibility target. WCAG 2.2 Level AA is the default. Adjustable for jurisdictions with stricter local requirements.
  • Data residency. The primary region where the brand record is stored. Defaults based on the atlas creation region; changeable on Guardian.
  • Data subject contact. The email address for data subject requests. Defaults to the brand owner; can be reassigned to a designated officer.

Documents and certificates

A list of administrative documents associated with the atlas:
  • Studio handover certificate. Generated at handover; signed by both sides.
  • Custom contracts. Optional. Upload any client-side contracts you want stored with the atlas.
  • Data processing addendum. Brand Atlas’s signed DPA for this atlas. See the DPA for the template.

Integrations

External system connections.

Account and profile

Your personal settings.

The brand record

What is being governed here.