synkMap the domains before adding them
Write down each domain, its DNS provider, its current email provider, and the person who can approve a change. Add the addresses that must keep working, including accounts used for invoices, password recovery, and customer enquiries.
For example, example.in and example.com might belong in one workspace when the same company controls both. An agency's client domains may need separate organisations and access arrangements. A convenient login should never replace a clear ownership decision.
- List domains and the business that owns each one.
- Identify the authorised DNS administrator.
- Record active mailboxes and any forwarding rules.
Add and verify each domain separately
In Synk, a workspace owner or admin can add more than one domain in that workspace. Follow the verification instructions for the particular domain being added. Copy its unique ownership record and the mail records shown in the setup flow.
A verified first domain does not verify a second one. Existing email may still be using the old provider, so prepare the required mailboxes and a change window before altering its mail routing. Keep a copy of the previous DNS values for reference.
Define what one login means for your team
One login lets an authorised owner or admin manage those domains from a single workspace. The same local name on two domains, such as sales@example.in and sales@example.com, represents two distinct addresses until you deliberately configure their handling.
Members are restricted to their own mailbox. Workspace owners and admins have organization-wide mail access under the current roles. Decide who should have that wider access and whether any address should be an alias. Self-serve alias management is not yet part of Synk's advertised pilot interface, so confirm that requirement before making it part of your rollout.
Prove the setup with a domain-by-domain check
Run a small acceptance check for each domain rather than assuming the second setup behaves like the first. Use an outside mailbox you control, send a message in both directions, check the sender address on replies, and confirm that the intended user can read it.
Review the domain-health screen after the records have updated. Then document which administrator owns future DNS changes and who should receive operational alerts. Synk is currently a controlled pilot; domain limits and final commercial terms must be confirmed during onboarding.
- Test inbound, outbound, and reply sender for every domain.
- Check that an ordinary member sees only their permitted mailbox.
- Keep the domain list and administrator responsibilities current.