---
title: "Run mail for clients"
description: "Keep every client in its own workspace, with its own domains, people and rules."
url: "https://openemail.uk/features/client-workspaces"
---

Inboxes a team works

# Run mail for clients one account, many workspaces

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

[Open mail](https://openemail.uk/mail/inbox) [Get Started](https://openemail.uk/signup.md)[Every walkthrough](https://openemail.uk/features/in-practice.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.

How it works

## Running in three steps.

1. 01
   
   One workspace per client
   
   Each holds its own domains, addresses, members and rules.
2. 02
   
   Invite the client in
   
   Give them a role, and only the addresses they own.
3. 03
   
   Switch between them
   
   The switcher at the top of the sidebar holds every workspace you can open.

What it runs on

## The parts doing the work.

Nothing here is a separate product. Each one is a piece of the mailbox you already have.

Multiple domains

Point several domains at one inbox, subdomains included.

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

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.

Share an address

Hand billing@ to the person who does the billing.

share with sarah@acme.com

SA

AL

NI

have access

Scoped visibility

One address means one address.

Sarah support@

Alex billing@

Nina careers@

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

Templates

A body written once, versioned, and sent many times: from the composer, from your own code, or by an agent.

Intro Invoice Follow-up

Hi Sarah, good to meet you at

Rules you write yourself

Your own conditions, and what should happen to anything that matches them.

deals@spammy.io blocked sender

anyone@spammy.io blocked domain

hr@recruit.co language filter

ci@acme.dev your rule → archive

REST API

A documented HTTP API with issuable, scopable, revocable keys.

/threads?query=invoice

{ "threads": 12 }

Same mailbox, whether a person or a program is holding 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

Nearby

## Other jobs for the same inbox.

Run a support inbox

Your team works one support address together, with labels, rules and saved replies.

Subject has refund

dana@northwind.co Refunds

omar@lumen.io Billing

Hand a mailbox over

An address belongs to the workspace, so the person changes and the mail stays put.

ops@northroad.com 09:14

kai@paleleaf.io 08:02

hello@ acme.com

DI RK

read send

Give every team an address

Make any address on your domain and hand it to the people who answer it.

hello@ acme.com SR read and send

press@ acme.com AK read

\*@acme.com catch-all

[Every walkthrough](https://openemail.uk/features/in-practice.md)