# Invite and manage people

> Source: https://elaichi.ai/docs/guides/members/invite-and-manage-people/

Bring colleagues into your organization, give them the right roles, and remove them without leaving broken shared tooling behind.

**Where to find it:** **Members & Roles → People**

You need the **Manage members** permission (`member:manage`) to invite people, change roles, revoke pending invites, or remove members. Anyone in the organization can see the People list.

## Ways people join

| Path | How it works | Starting role |
| --- | --- | --- |
| **Invite** | You email a single-use activation link with pre-assigned roles. | The roles you select on the invite (at least one). |
| **Verified domain** | Someone with an email on a verified org domain signs in and joins automatically. | The domain’s default role, or **Member** if none is set. |
| **SCIM** | Your identity provider provisions users (and optionally groups). | Group → role mappings when configured; otherwise **Member**. |

Invites are the day-to-day path. Domain join and SCIM are the invite-free paths — see [Provisioning members with SCIM](/guides/sso/scim-provisioning) and your domain settings under **Settings → Organization** / **Settings → SSO**.

## Invite someone

1. Open **Members & Roles → People**.
2. Choose **Invite member**.
3. Enter their **exact** work email — the activation link is bound to that address.
4. Select **at least one role** (built-in or custom). People can hold several roles; permissions add up.
5. Choose **Send invite**.

Elaichi emails a **seven-day** single-use link. The dialog also shows the raw invite link **once** so you can copy it for chat or a ticket if email doesn’t arrive. Anyone with that link can activate the account for the invited email — treat it like a secret.

**You'll know it worked when:** The person appears under **Pending invites** until they click the link, then moves into the People list with the roles you chose.

### What happens when they accept

Clicking the link proves the invited email, creates or finds their user account, accepts the invite, and starts a session — they don’t need a separate magic-link login for that first join.

## Pending invites

Below the People table, **Pending invites** lists emails that haven’t joined yet.

| Action | Effect |
| --- | --- |
| **Revoke** | Cancels the invite. The link stops working. |

There is no resend control in the UI — revoke and send a new invite if the link expired or was lost.

## Change someone’s roles

1. Find the person in the People list.
2. Open the roles control on their row.
3. Tick or untick roles. Changes apply immediately — including to people who are already signed in.

**Member** is the usual default for new joiners. Prefer starting narrow and adding permissions later rather than assigning **Org Admin** broadly. See [Roles and permissions](/guides/members/roles) for the full catalog.

People can also belong to **teams** (shown on the same row). Team membership is managed under **Members & Roles → Teams**, not on the invite dialog.

## Remove a member

Removing someone immediately cuts their access to the organization. Before that finishes, Elaichi runs an **offboarding** check on every **personal** connection they own.

1. Open the row menu → **Remove from organization**.
2. Review each personal connection:
   - Connections used by shared toolboxes are flagged **Used by shared toolboxes**.
   - Connections nothing else depends on are listed without that flag.
3. Choose an action per connection (defaults are chosen for you — change them before confirming):

| Choice | Use when | Default when |
| --- | --- | --- |
| **Transfer to organization** | Everyone should keep using the account | Connection is referenced by shared toolboxes |
| **Transfer to team** | One team owns that system | You pick the team |
| **Transfer to member** | A specific colleague is taking it over | You pick the member |
| **Delete connection** | Truly personal, and nobody else needs it | Connection is not referenced |

4. Confirm **Remove member**.

If a referenced personal connection isn’t resolved, removal is refused until you transfer or delete it. Unreferenced personal connections you leave on **Delete** are cleaned up with the member. Credentials move with a transfer — toolboxes that already used the connection keep working.

You can’t remove yourself from the People list. The last **Org Owner** can’t be removed or demoted until someone else is an Owner.

For the full transfer flow outside of removal, see [Transfer and offboard](/guides/connections/transferring-and-offboarding).

## Good to know

- Invites require `member:manage`. Role assignment and removal use the same permission.
- An organization always keeps at least one **Org Owner**.
- New joiners via domain or SCIM (with no group mapping) get **Member** unless you configure another default.
- After someone joins, add them to teams under **Teams** so shared connections and toolbox shares reach them as a group.

## Related

- [Accept an invite](/guides/basics/accept-an-invite)
- [Roles and permissions](/guides/members/roles)
- [Organize people into teams](/guides/members/teams)
- [Transfer and offboard](/guides/connections/transferring-and-offboarding)
- [Provisioning members with SCIM](/guides/sso/scim-provisioning)