---
title: "Invite team members by email"
description: "Invite anyone to your workspace by email, account or not. The role and mail you pick arrive the moment they accept, and nothing is granted before that."
url: "https://openemail.uk/features/invites"
---

[Workspaces & team](https://openemail.uk/features.md#team)

# Invitations Access that waits for a yes.

Type an address, pick a role and the mail they may reach. Account or not, they get a link, and nothing is theirs until they accept.

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

In short

## How do team invitations work?

A team invitation is a link emailed to someone so they can join a shared workspace. It usually names what they may reach, and nothing should be granted until they accept.

14 days

before an unanswered link expires

256 bits

of randomness in every link

100

unanswered invitations a workspace can hold

200

sent in a rolling day, per workspace and per person

How it works

## Access travels inside the invitation

The role, addresses and whole domains you choose ride along, and accepting grants exactly that. Until then, no permission check reads it.

## The link and the sign-in agree

The link proves they read that inbox, and the sign-in proves who is accepting. Signed in as somebody else, they see both addresses named and an offer to switch.

## Send it again, or take it back

Sending again mints a new link, restarts the fortnight and retires the old one. Withdrawing kills the link at once.

What you get

## In the product today

Hashed at rest

The database keeps only a keyed hash, so a leaked backup opens nothing.

Listed apart

The members screen lists them separately, showing what each person will get.

Asking twice renews

Inviting the same address again refreshes the open invitation rather than adding a second.

Same over the API

POST /members answers 202 with an invitation, whoever the address belongs to.

Good practice

## Getting the most out of it

1. 01
   
   Tick access up front
   
   Pick addresses or domains in the invitation, or they join seeing the workspace and nothing more.
2. 02
   
   Invite the sign-in address
   
   Only that address can accept it, so send it where they actually sign in.
3. 03
   
   Share whole domains
   
   A whole domain covers addresses made on it later, so the next one needs no new invitation.

Questions

## Asked often

Keep going

## Works well with

Share an address

Hand billing@ to the person who does the billing.

Roles & permissions levels

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

Scoped visibility

One address means one address.

Start

## Your domain, your mail.

Point a domain at OpenEmail and read it in a mailbox built around it. The free plan covers one domain.

[Open mail](https://openemail.uk/mail/inbox) [Get Started](https://openemail.uk/signup.md)[Read the reference](https://openemail.uk/docs/knowledge/team/invites.md)