Skip to main content
For Guardian-tier customers, Brand Atlas supports custom domains and white-label branding. The atlas can be reached at your domain (brand.yourcompany.com), with the Brand Atlas wordmark and footer replaced or removed.
Custom domain and white-labelling are Guardian-tier features. Some configurations are in pre-general-availability beta through 2026. The full set listed below reflects the planned release; check Settings → Domain and white-labelling for what is currently available on your account.

​
What custom domain means

By default, your atlas is reached at app.brandatlas.pro/[your-atlas]. With custom domain configured, your team reaches the atlas at a subdomain of your own choosing: brand.acme.com, atlas.yourcompany.com, or similar. The portal still runs on Brand Atlas infrastructure; the custom domain is a vanity layer in front of it. The brand record, the team membership, the billing, and everything else are unchanged. The URL is the visible difference.

​
What white-labelling means

White-labelling removes or replaces Brand Atlas’s own branding on the team-facing surface:
  • The Brand Atlas wordmark in the top-left of the portal. Replaced with your atlas’s name and logo, or hidden.
  • The Brand Atlas footer. Removed or replaced with your own footer.
  • The Brand Atlas favicon. Replaced with your atlas’s favicon.
  • Outbound emails. Notification emails sent from notifications@brandatlas.pro are sent from notifications@yourdomain.com instead.
  • The sign-in page. A custom sign-in page at your custom domain.
What does not change:
  • The legal layer. Brand Atlas remains the operator of the underlying service. Terms of service, privacy policy, DPA, and similar are still Brand Atlas’s.
  • System status. Status communication remains Brand Atlas’s; see Status for the current channels.

​
Setup walkthrough

1

Choose the subdomain

Decide on the subdomain. brand.yourcompany.com is the most common shape. Avoid the root domain itself (yourcompany.com); the root usually has other duties.
2

Add the CNAME

In your DNS provider, add a CNAME record pointing the chosen subdomain at proxy.brandatlas.pro. The exact target is shown in Settings → Domain and white-labelling → Setup.
3

Verify in Brand Atlas

Click Verify domain. Brand Atlas checks the CNAME and provisions an SSL certificate. The check usually completes within five minutes; DNS propagation can extend this to a few hours.
4

Configure the white-label elements

Upload your atlas’s logo (light and dark), favicon, and any footer text or links. Choose whether outbound emails come from your domain (requires additional DNS setup for SPF, DKIM, DMARC).
5

Switch over

Click Activate custom domain. The atlas becomes reachable at your domain. The original app.brandatlas.pro URL also continues to work, redirecting to the custom domain.
The custom domain is live. Your team can update their bookmarks; future invitations use the custom domain by default.

​
Email-sender domain

Sending notification emails from your own domain requires:
  1. SPF record. Authorises Brand Atlas’s mail servers to send on your behalf.
  2. DKIM record. Signs the outbound mail with a key Brand Atlas provides.
  3. DMARC alignment. Your DMARC policy must permit sub-domain alignment.
Brand Atlas provides the exact DNS entries needed during setup. Your IT team adds them to your DNS. If you do not configure the email-sender domain, notification emails come from notifications@brandatlas.pro even when the portal is on your custom domain. The team will see a Brand Atlas sender address; the rest of the experience is on your domain.

​
Multiple atlases on multiple domains

A team running multiple atlases (an agency, a holding company with several brands) can configure custom domains per atlas. Each atlas’s setup is independent. A single atlas cannot be reached at more than one domain. If you need both brand.acme.com and atlas.acme.com to reach the same atlas, set up one as a redirect to the other in your DNS.

​
What the team sees

After setup, team members see:
  • Your domain in the URL bar.
  • Your atlas’s logo in the portal sidebar.
  • Your footer text and links.
  • (If configured) outbound emails from your domain.
They still receive notifications, raise Update Requests, and use search the way they always have. The functional surface is unchanged.

​
Disabling custom domain

To stop using the custom domain (a domain change, a brand evolution, a decision to consolidate), open Settings → Domain and white-labelling → Deactivate. Confirm. The custom domain stops resolving to the atlas; app.brandatlas.pro continues to work normally. DNS changes on your side may take time to propagate. Keep the CNAME pointed at Brand Atlas for at least 24 hours after deactivation to avoid mid-flight errors.

Brand identity settings

The brand-level settings.

Integrations

Connecting external tools.

Guardian in detail

Where this feature lives.