Running multiple White Label brands

White Label branding is configured per domain, so one TrekMail account can use a shared account-default brand or a different custom profile on each domain. Each domain has its own Branding tab, where you can choose the source, identity, and the Dashboard or Webmail hosts to publish. This article explains the choices and the checks to make before you create a second account.

Branding is per domain

Go to Domains → (select a domain) → Branding and you'll find a Branding source selector for that domain:

• Use account default: inherit the account-wide default brand.
• Custom for this domain: give this one domain its own brand identity.
• Off: no White Label branding for this domain.

Because the brand lives on the domain, an agency or reseller can serve several clients from one TrekMail account, one domain per client, each with its own look. There's no need for a separate account per brand just to get a separate brand.

Setting an account default and applying it everywhere

If most of your domains should share one brand, set it once and roll it out:

1. Open the Branding tab for any domain and configure the brand identity.
2. In Apply changes, turn on Make this the account default so new domains inherit it.
3. Turn on Apply to all existing domains to queue the shared settings for existing domains. Then review every domain's source, host labels, DNS records, and status; a saved profile does not make every host immediately ready for customers.

You can still override an individual domain by switching its Branding source to Custom for this domain. The useful pattern is to set the shared identity once, then review and publish hosts domain by domain rather than assuming a bulk save copied DNS or completed certificates.

When you actually need separate accounts

Multiple domains in one account can cover a shared operating model. Consider separate TrekMail accounts when you need a genuinely separate owner, billing relationship, access boundary, or off-boarding process:

• Separate billing entities. Each TrekMail account has its own invoices, subscriptions, and Stripe customer record. If two brands must be billed as distinct legal/accounting entities, give each its own account.
• Fully isolated customers. If two sets of customers must never share an admin surface, mailbox pool, or usage view, keep them in separate accounts.

If a shared account is appropriate, use per-domain custom branding and review access before inviting anyone. If the choice has legal, privacy, or billing consequences, decide it with the people responsible for those areas rather than relying on branding alone.

Tradeoffs of running multiple accounts

If you do split across accounts for billing reasons, keep these in mind:

Cost. Plans and add-ons are configured and billed in each account. Check the current currency, price, promotion, and tax treatment in the relevant checkout rather than assuming an account-wide or multi-account discount.

Administration overhead. Each account has its own context, domains, and White Label settings. A person can switch only between accounts they have been given access to. Do not promise a central reseller view or shared administration across accounts unless it is available in the current product.

Separate billing. Separate accounts create separate billing work. Before splitting, check who will own the account, receive invoices, handle payment failures, and approve access changes.

Separate support escalations. A ticket opened from one account is tied to that account.

Account-level features stay per-account. Two-factor authentication, mailbox limits, sending volume caps, and similar settings are configured per-account.

When multiple domains in one account makes sense

A few patterns work well:

Agency serving several customer brands. Each customer can have a domain with its own custom brand identity. Keep a clear internal record of the domain owner, the active customer-facing hosts, and who may administer that domain.

Distinct sub-brands of one company. Your company runs two or three consumer-facing brands that should look unrelated. Add a domain per brand and set each Branding source to Custom for this domain.

A shared house brand with exceptions. Set an account default, apply it to the domains that should inherit it, then override the domains that need something different. Review the result and host status after the bulk action.

When separate accounts makes sense

Separate billing entities. Separate accounts can be appropriate when the account owner, invoice recipient, payment method, or legal process truly must be separate.

Fully isolated customer pools. Two customer bases that must never share an admin surface, mailbox pool, or usage view.

Different regions or currencies. Confirm the current billing and data-processing terms before you make an account split for regional or currency reasons. Branding alone does not create a separate regional service.

A consolidated agency workflow

For a multi-brand agency on a single account:

• Set a sensible account default so new domains start on-brand, then customize the domains that need their own identity.
• Document each domain's specifics. Keep internal docs mapping each branded domain to its client, branded URLs, customer contact, and any quirks.
• Standardize the per-domain setup. For each client domain, add the domain, choose the Branding source, save the identity, enable only the hosts you will publish, and copy each CNAME that needs attention from Branding. Select Check now and wait for Active before sending that host to a customer. Completed records remain available under Show records already working. Document the final hostname and support contact for every domain.
• Escalate true multi-entity needs. If you need separate ownership, billing, compliance commitments, or a capability not visible in the product, contact support with the account and domain scope. Do not assume an unsupported cross-account feature will be available.

Common scenarios

"I have several clients and want each to have its own brand." Add a domain for each client, set the Branding source to Custom for this domain, configure the identity, and publish only the hosts you have tested. Decide separately whether one shared account is appropriate for billing, support, and access.

"I want all my domains to share one brand." Configure the brand on one domain, then turn on Make this the account default and Apply to all existing domains in the Apply changes section. Review the result on every domain before publishing its host.

"I want different brands on different domains but billed together." Per-domain custom branding can support that model. Confirm the account-level billing, permissions, and customer-support implications before treating it as your production structure.

"I want two brands billed as separate companies." A separate account may be appropriate when ownership and billing must be independent. Confirm the migration, access, and invoice process before you create it.

"Can I use the same branded subdomain for two domains?" A branded hostname must be unique. Branding checks the full hostname you create from the label and domain, so copy the displayed value and choose another valid label if it conflicts. Dashboard and Webmail also cannot use the same label on one domain.

What's next

• What is White Label Lite?: overview.
• Set up White Label Lite: per-domain activation and DNS steps.
• Eligibility and plan changes: plan requirements.