---
title: "Running mail for clients - OpenEmail"
description: "Run email for every client in a workspace of its own, with their domains, their people and their sending kept apart from yours"
url: "https://openemail.uk/use-cases/client-work"
---

Mail run for clients

# Take on clients without mixing the mail

Each client gets a workspace of their own: their domains, their addresses, their people. You switch between them at the top of the sidebar, and nothing crosses over.

[Open mail](https://openemail.uk/mail/inbox) [Get Started](https://openemail.uk/signup.md)[All use cases](https://openemail.uk/use-cases.md)

Workspaces

NR HV PL BC

northroad.com

hello@ @northroad.com

billing@ @northroad.com

press@ @northroad.com

AB KM members 6 filters

Pick a client in the workspace switcher. Its domain, addresses and people come with it.

Where it starts

## What this looks like today.

Every client has their own domain

Their mail leaves on a domain you do not own, so the records have to prove it is theirs.

You sign in and out all day

One account per client, and reading their mail means leaving yours behind.

The client wants a seat

They ask to see their own address, not everything else sitting in the workspace.

How it works

## Running in four steps.

1. 01
   
   Make a workspace per client
   
   Each one holds its own domains, addresses, members and rules, under the account you already have.
2. 02
   
   Add their domain and publish
   
   Copy the ownership, signing and routing records into their DNS, or sync them in one press where supported.
3. 03
   
   Invite the client in
   
   Give them a role and grant only the addresses they own, since one address means one address.
4. 04
   
   Switch between them in the sidebar
   
   Pick a client and its domains, addresses and people come with it, while your own mail stays put.

What it runs on

## The parts doing the work.

What a client workspace is built from, and what the client can and cannot see once they are in it.

Workspace branding

Put your own mark and logo in the sidebar, in place of ours.

acme.com acme.dev studio.acme.com

hello@ acme.com delivered

billing@ acme.com delivered

oct-2026-signup@ acme.com delivered

anything-at-all@ acme.com delivered

Roles & permissions levels

A role says what somebody may do; an address grant says what they may do it to.

Sarah support@

Alex billing@

Nina careers@

read, or read and send as it, with nothing else visible

Invitations

Share with someone who has not signed up yet and have them invited.

billing@acme.com shared

SSarah AAli JJamie NNadia

No seat added. The bill does not move.

Multiple domains

Point several domains at one inbox, subdomains included.

acme.com acme.dev team.acme.com hey.acme.io

DMARC policy

A starter p=none record, printed to copy or written by a sync, never tightened for you.

TXT \_dmarc.acme.com

v=DMARC1; p= none; rua=…

Optional watch only

Analytics & graphs

What your mailbox is actually doing, drawn rather than guessed at.

62 on Monday · 38 still waiting on you

Scoped visibility

One address means one address.

Sarah support@

Alex billing@

Nina careers@

read, or read and send as it, with nothing else visible

In practice

## Every piece, walked through.

Four shorter walkthroughs: keeping clients apart, proving a domain, reading what happened after send, and signing every send the same way.

Run mail for clients

Keep every client in its own workspace, with its own domains, people and rules.

NR HV PL BC

northroad.com

hello@ @northroad.com

billing@ @northroad.com

AB KM 6 filters

Lock down your domain

Publish the records that prove your mail is yours, and check what your domain says in public.

yourdomain.com Records found

TXT @

CNAME oe1.\_domainkey

TXT \_dmarc

MX @

Watch what happens after send

See what happened to every send, and keep dead addresses out of the next one.

omar@lumen.io Skipped

Delivered 129

Bounced 3

Blocked omar@lumen.io Held back

One sign-off everywhere

Set the sign-off once, and every address and every send path uses it.

From hello@acme.com shared

AC Acme The whole team acme.com

Questions

## Asked before signing up.

Can a client see the other clients I work for?

No. A workspace holds its own domains, addresses, members and rules, and the switcher only shows workspaces that person can open. An address grant covers that one address.

Do I need a separate account for each client?

No. One account, one workspace per client. Pick a client in the workspace switcher and its domain, addresses and people come with it.

Does OpenEmail tighten a client's DMARC policy for me?

No. Adding a domain gives you a starter p=none record to copy or sync. Moving past p=none is a change you make in their DNS yourself, once you are happy with what is signing.

Nearby

## Other jobs for the same mailbox.

Put the whole company

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.

DNS records Verified

MX @

TXT @

ben@ acme.com BW

anna@ acme.com AL

Mail that belongs to a job

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.

AP Anna Petrova PDF

JO Jonas Ortiz PDF

Files 2

anna-petrova-cv.pdf 240 KB

jonas-ortiz-cv.pdf 188 KB

Keep your domain yours

Publish the records that prove your mail is yours. Every message that arrives comes scored, with the sender checks and the reasons on it.

yourdomain.com Records found

TXT @

CNAME oe1.\_domainkey

TXT \_dmarc

MX @

[All use cases](https://openemail.uk/use-cases.md)
