Put the whole company
on a domain you own
Addresses for people and for roles, all on one domain. Each has its own people, keeps the shared sign-off, and stays put when somebody leaves.
Three records turn the domain on. Then each address gets its people.
Where it starts
What this looks like today.
hello@ lands in one person's inbox
Press, jobs and billing all reach whoever set them up, and forwarding keeps them there.
Somebody left and the mail went too
The address was theirs rather than the company's, so the threads walked out with the laptop.
Nobody can say who reads what
Access was handed out one favour at a time, and no list says who holds which address.
How it works
Running in four steps.
- 01
Add your domain
Settings, Domains, Add. OpenEmail prints the records your DNS needs, a starter DMARC line included.
- 02
Publish the records
Paste them at your DNS host, or connect the host and sync them. The domain then starts receiving.
- 03
Create the addresses
Add hello@, press@ and jobs@ on that domain, and leave catch-all to answer whatever else arrives.
- 04
Invite the people who answer
An invitation carries the role and the addresses. Nothing is granted until the person accepts it.
What it runs on
The parts doing the work.
This runs on parts you can read about on their own: domains and DMARC, roles and grants, invitations, the shared sign-off, contacts and account security.
Point several domains at one inbox, subdomains included.
A starter p=none record, printed to copy or written by a sync, never tightened for you.
v=DMARC1; p=none; rua=…
A role says what somebody may do; an address grant says what they may do it to.
read, or read and send as it, with nothing else visible
One address means one address.
read, or read and send as it, with nothing else visible
Hand billing@ to the person who does the billing.
In practice
Every piece, walked through.
Each page below walks one job inside it, from turning the domain on to handing a mailbox over and answering in somebody else's language.
Give everyone at your company an address on your domain, and decide who reads what.
Make any address on your domain and hand it to the people who answer it.
An address belongs to the workspace, so the person changes and the mail stays put.
Everyone works from the same contacts, and your code and agents read the same rows.
Questions
Asked before signing up.
Do we have to move our DNS to OpenEmail?
No. Paste the printed records at the DNS host you already use, or connect that host and let a sync write them. The domain stays where it is and stays yours.
Can somebody read an address they were not given?
No. A role says what a person may do, and an address grant says which addresses they may do it to. One address means one address, and taking a member out revokes every grant they held.
Does OpenEmail set our DMARC policy for us?
Only the starter record, p=none, printed for you to copy or written by a sync. Tightening it to quarantine or reject is a decision you make at your DNS host. OpenEmail never tightens it for you.
Nearby
Other jobs for the same mailbox.
sales@, jobs@ and billing@ get worked by several people at once, each with their own access. Nothing is forwarded, and nobody leaves with the address.
