Members are the people in an organization. Admins manage the list on the **Members** page in the console. Personal spaces have no members.

## Invite people

1. Open **Members** and click **Invite members**.
2. Enter one or more email addresses and choose a role: **Admin** or **Member**. See [Roles & permissions](/docs/roles).
3. Send. Each person gets an email with a link.

An invitation appears in the list with status **Pending** until it is accepted. Pending invitations count toward the organization's member limit.

### What the invited person sees

The link opens a page that shows who invited them and which organization they are joining. They must sign in with the **same email address the invitation was sent to**. If they are signed in with a different address, the page says so and does not accept the invitation. This stops a forwarded link from adding the wrong account.

After they accept, they land in the organization's default workspace. They can also decline.

### Expiry, resend, and revoke

- An invitation expires after a set period (7 days by default). An expired link cannot be used, and it says so.
- **Resend** sends a fresh link and replaces the old one. You can resend one invitation about once a minute.
- **Revoke** cancels a pending invitation.
- Email addresses are matched exactly. `ana+work@example.com` and `ana@example.com` are different addresses.

If an email does not arrive, resend it. The link is only in the email, so there is nothing to copy from the console.

## Change a role

On the Members page, open the menu on a member's row and choose a new role. Every organization must keep at least one admin, so the last admin cannot be demoted or removed.

## Remove a member

An admin can remove a member from the row menu. They lose access to the organization immediately.

## Leave an organization

You can leave an organization from your own row on the Members page, or from **Organizations** in Account settings (open it from your avatar menu). If you are the only admin, you cannot leave. Make someone else an admin first.

## What happens to a member's API keys

Every API key has an owner. When its owner leaves or is removed from the organization:

- Their keys stop working at once and are turned off. In the key list they show **Owner removed**.
- If the person is invited back, the keys stay off and show **Disabled**. They cannot be turned back on: an admin deletes them and creates new ones.

Keys are tied to their owner, not to the person who created them. An admin who creates a key for a teammate makes the teammate its owner. See [API keys](/docs/api-keys).

## Budgets for a member

An admin can set a spend limit on a member. It counts everything spent with keys that person owns, across all workspaces in the organization. See [Budgets](/docs/budgets).