One owner can manage a studio, a shop and a training business in one TrekMail account. Sharing the account doesn't mean that every employee should see every brand. Start with a responsibility map so the convenience of one dashboard does not become uncertainty over who handles each inbox.
Build a brand-by-brand access sheet
Give each domain a row with its mailbox owner, people who may manage it, reply address, SMTP route and expected storage. Then look at the sheet as a shop employee: which shop tasks are necessary, and which studio or training resources should remain outside that role? Check management access and mailbox access separately. Domains in one account also share account-level resources; separate brand names do not create independent storage budgets or billing accounts.
Separate the account, domains, and mailboxes
The account brings together service management and resources. A domain supplies the part of an email address after @. A mailbox stores messages and gives access to an individual or the members of a shared mailbox.
The studio might use anna@studio.example and hello@studio.example. The store has its own sales@shop.example and orders@shop.example. Using the word sales on two different domains does not automatically connect those addresses.
Start with a three-level outline: account, domains, mailboxes. Add the person responsible for each mailbox. This helps during setup and later when staff change or a project gets its own administrator.
Connect each domain separately
Add the domains to TrekMail and obtain the DNS settings for each. DNS records tell other services how to find a domain's website or email. MX records specify where incoming messages should go.
Check each domain individually, even if you bought all of them from the same registrar. The store may already have email with another provider, while the new training business has none. For an active domain, prepare the addresses and a plan to move old messages before changing the delivery route.
The guide to adding domains covers both individual setup and bulk import. Importing a list saves work, but DNS checks still apply to each domain separately. One domain passing its checks doesn't mean the entire list is ready.
Decide which addresses should share a mailbox
An owner may want inquiries from two projects to reach one mailbox through authorized additional addresses. A store employee and a teacher will usually benefit from separate mailboxes because they have different work, correspondence, and message history.
If several people answer support@, consider a shared mailbox with individual permissions. If one person receives mail under two names for the same role, an alias may be enough. Combine addresses when it supports the work, rather than just shortening the address list.
Assign administrative access according to responsibilities as well. Give each person the appropriate role and domains. Managing a domain and signing in to a mailbox are different actions, so check both separately. A client management interface under your own brand requires the relevant White Label setup.
Review one ordinary request and one boundary case
Walk through a request from each brand. The shop may need a new address for returns, while the studio needs to remove access for a contractor and the training business needs to change a sender name. For each request, name the person who approves it and the person who performs it. A single owner can approve all three, but that does not mean every employee needs the owner's dashboard login.
Next, consider a request that crosses a boundary: a shop employee asks to read a studio mailbox because they occasionally cover the telephone. Decide whether this is a real ongoing responsibility or whether forwarding one specific enquiry would be enough. If ongoing mailbox access is appropriate, grant it deliberately through the supported access mechanism and record why. Do not use a shared brand name as a substitute for deciding who may read the correspondence.
Check the resulting account as the employee who will use it. Seeing the right domain list is one part of the check; being able to perform the intended mailbox task is another. A narrow management role and a mailbox sign-in have different effects. Avoid putting customer passwords into the access sheet to make the process appear simpler.
Decide what changes if a brand leaves
One account is convenient while the same owner controls the businesses. Before combining them, ask what would happen if the shop were sold or the training project became a separate company. Identify who controls the domain registration, who can approve an archive transfer and which people will need new access arrangements. Plan the domain transfer and any stored-mail transfer as separate tasks.
Keep business-specific records readable without the rest of the account's secrets. A handover should identify that brand's domains, mailboxes, authorised senders and support contact. Any required transfer of messages or files needs a separate plan and verification. Check current service capabilities before promising a one-click separation.
Allocate responsibility for shared capacity
Review the busiest brand's storage alongside the quieter ones. If the studio keeps large attachments, give someone responsibility for watching its usage and discussing retention with the team. Agree retention changes with the responsible brand before removing stored correspondence.
Agree how the owner will apportion the account cost internally if the businesses need separate budgets. The names in a domain list do not create separate invoices or independent resource pools. A simple internal cost record may be enough under one owner; separate commercial or administrative requirements may justify a different account arrangement. Make that decision before presenting the setup to employees as three independent services.
Set up sending and allow for shared resources
Choose how each domain will send mail. SMTP carries outgoing messages. In TrekMail, a domain can use built-in SMTP on Starter, Pro, or Agency, or a saved profile for an external provider. You can choose a default for new domains. See the guide to SMTP routing by domain.
Check the sender name and signature for each business. Someone receiving a message from the store should see the store's address, even when the owner handles several projects in one interface.
Estimate total storage next. A studio's attachment-heavy archive may use the shared allowance faster than correspondence for the training business. Compare the combined domains, mailboxes, and storage with the plan's limits.
Related reading
- Multi Domain Email Hosting: Scale Without Losing Control
- Forty Domains, One Account, and No Spreadsheet
- Five people, fifteen email addresses: what are you paying for?
- How do I stop replying from the wrong business address?
- How do I keep two brands on different SMTP providers?
