# Invite a colleague, and what a seat costs

> Three ways to add somebody, three roles, and how seats are counted per organization.
> https://facteur.eu/en/help/membres-et-sieges

Everything happens from [**Settings → Members**](https://app.facteur.eu/settings/members).

## Add somebody

Three ways, depending on what you know about the person.

| What you want to do | How to do it |
|---|---|
| Invite somebody whose address you know | **By email.** The invitation goes to the address you give |
| Pass the invitation on yourself | **By personal link.** The same invitation, but you get the link. Useful when the mail does not arrive, or when the person prefers another channel |
| Onboard three people in one morning | **By organization link.** A short-lived link, with its role, its validity, a number of uses and a revoke button |

The joining pages `/join/<token>` and `/invitations/<id>` open **without an account**:
the invitee sees who is inviting them before signing up.

## Choose the role

| Role | What they can do |
|---|---|
| **Owner** | Everything, including changing the shape of the organization and deleting it |
| **Administrator** | Manage inboxes, members, workspaces and SSO |
| **Member** | Read the inboxes of the workspaces they belong to |

A member sees the organization form read-only, and the danger zone appears to owners
only.

## Count the seats

A seat is a member of the organization. The ceiling comes from your plan and is counted
**for the organization**, not per workspace: adding somebody to a second workspace does
not use a second seat.

When the ceiling is reached, the invitation is refused and the answer names the plan
that would allow it. It is never accepted and then silently inert.

## Remove somebody

Remove the member from
[**Settings → Members**](https://app.facteur.eu/settings/members). Their access is cut.

**Allow up to five minutes** before a session that is already open stops answering: the
session cookie carries its own signed copy, and deleting a row in the database does not
reach a cookie already sitting in a browser.

If the departure is sensitive, do not stop there: revoke the API keys the person was
using, see [API keys](cles-api), and go through
[Account and security](compte-et-securite).

## Known limits

- **No workspace role beyond member and administrator.**
- **No banning.** You remove an access; you do not stop an address from coming back on
  invitation.