# People and roles

Invite people to your board, decide who can change what, and keep a team's cards to the people on it. Everyone has one
of three roles, and each role can do everything the ones below it can:

- **Member**: adds, runs and reviews their own cards, and adds their own machines.
- **Admin**: also changes teams, recipes, automation and connections, invites and removes people, reads the audit log,
  and exports the board.
- **Owner**: also hands ownership on and deletes the board.

Whatever your role, you change, run and answer only **your own cards**, and drive only **your own machines**. An admin
who needs to finish a departed person's cards takes them over (below). The full list of actions and the lowest role for
each is in [Who can do what](https://andon-docs.pages.dev/reference/permissions.md).

When your role is too low for something, the board says so: *Only owners and admins can add teams.*

## Invite someone

1. Open **Settings → Workspace**.
2. Beside **People**, press **Invite someone**.
3. Type their **Email**, pick **Member** or **Admin**, and press **Send invite**.

They get an email with a link that works once, for that address, for seven days. If the email can't be sent, the
board shows the link instead: **Copy** it and send it yourself. It isn't shown again. Waiting invites are listed under
the form, where you can resend or **Revoke** one.

A person who joins opens a welcome page that helps them connect a machine.

An invite is the only way onto a board that already exists: an instance holds one org, so someone who signs up
without an invite is told to ask an admin for one. Another org needs another instance.

## Change someone's role

1. Open **Settings → Workspace** and press **Manage** beside **People**.
2. Pick **Member** or **Admin** in the person's row.

The list shows each person's cards and machines. To hand the board to someone else, press **Make owner** on their row
and confirm **Transfer ownership**: they become the owner, and you stay on as an admin.

## Remove someone, or leave

- **Remove** on a person's row takes their access away now and revokes their machines here. Their cards stay until
  someone takes them over. An owner can't be removed.
- **Leave**, under **Danger zone** in the same sheet, takes you off the board and revokes your machines. To come back,
  someone has to invite you again. The last owner transfers ownership before leaving.

## Take over a departed person's cards

Nobody can change a card whose owner left. To finish or archive them:

1. Open **Settings → Workspace**, press **Manage** beside **People**, and find **Cards of people who left**
   (it shows once someone has left).
2. Press **Take over** beside the person.

The cards become yours, and you are added to any private team they were on.

When a person's account is deleted, their cards and machines belong to nobody. A card that belongs to nobody runs on
no one's machine and can't be moved to one: nobody can start it, a run Andon starts for it (a review round, a
pipeline step, Autopilot) waits, and its line says *nobody owns this card any more*. These cards are listed as
**Deleted accounts** under **Cards of people who left**; take them over to run them. A machine that belongs to nobody
runs no one's cards, and only an owner or admin can drive it.

## Keep a team private

A team is seen by everyone on the board, or only by the people chosen. A private team hides its sub-teams and
everything on its cards, from people and their machines alike. A new team is private to whoever made it.

1. Search Settings for **Who sees it** and pick the team.
2. Choose **Everyone on the board**, or **Only the people chosen** and tick who.

On a private team, only the people on it change who sees it; on a team everyone sees, owners and admins do. Roles don't
see past it: an owner or admin sees a private team only when they're on it. People with cards on the team must stay on
the list. When everyone leaves a private team, it goes to the board's owners.

When someone else's machine syncs a repository that belongs to a private team they aren't on, **Settings → Teams**
marks the team *Not shared with …*, and its **Who sees it** names them, so the people on it can decide whether to
share it.

## People from an import

An [import from a tracker](https://andon-docs.pages.dev/guide/import-from-a-tracker.md) can name people who aren't on the board yet. They become **former
members**: their name shows on their cards and comments, and their email stays private. When someone joins with the
same address, they take the former member's place.

Owners and admins manage them under **Settings → Workspace → People → People from imports**:

- **Invite** someone the tracker gave an email for, as a member or an admin. The invite is sent without the board ever
  showing their address.
- Link a former member to an existing member whose tracker address was different: pick the member in their row.
  **Not linked** undoes it.

## The audit log

Every admin and owner action is recorded: who did it, how (in person, through the chat, from a machine, or by Andon
itself), what, and the values before and after. Read it at **Settings → Workspace**, **Audit log**. Work on your own
cards isn't there; each card's history has it.

## Machines

Anyone on the board can add a machine, and it is theirs: only its owner drives it. Owners and admins can revoke any
machine, and removing someone, or their leaving, revokes theirs. Whatever a person's role, a machine's own
[policy](https://andon-docs.pages.dev/reference/policy.md) has the last word over what runs on it.
