Invite and manage people
Bring colleagues into your organization, give each person the right role, and remove people without leaving shared tools broken. A member is a person who belongs to your organization.
Where to find it: Settings → People → Members
Before you start
| Permission | What it allows |
|---|---|
Manage members (member:manage) |
Invite people, resend or revoke invites, change roles, and remove members. |
| None | See the People list. Every member can. |
You can only give a role that includes permissions you hold yourself. A role with a permission you lack is greyed out. This keeps anyone from granting more than they have.
Ways people join
| Path | How it works | Starting role |
|---|---|---|
| Invite | You email a single-use link with a role already chosen. | The role you pick on the invite. |
| Verified domain | Someone with an email address on a verified organization domain signs in and joins automatically. | The domain's default role, or Member if none is set. |
| SCIM | Your identity provider creates users and, optionally, groups. | The mapped role for their group when you set one up, otherwise Member. |
Invites are the everyday path. Domain join and SCIM need no invite. See Provisioning members with SCIM, and the domain settings under Settings → Domains.
Invite someone
- Open Settings → People → Members.
- Choose Invite member.
- Under Email addresses, enter each person's exact work email address. You can paste several addresses at once. The link works only for the address you enter.
- Under Role, pick one role, built-in or custom. Each person holds exactly one role, and it is everything they can do.
- Choose Send invite (or Send N invites for several addresses).
Elaichi emails each person a link that works once and expires in 7 days. The results screen tells you, address by address, whether the email went out.
You will know it worked when each person appears under Pending invites until they accept, and then appears in the People list with the role you chose.
If Elaichi could not send an email, the results screen shows the invite link for you to share another way. Anyone who has that link can activate the account for the invited address, so treat the link like a secret. You must tick I understand who this link lets in before you finish.
When a person selects the link, Elaichi confirms their email address, creates or finds their account, accepts the invite, and signs them in. They do not need a separate magic-link sign-in for that first join.
Manage pending invites
Pending invites sits below the People table and lists addresses that have not joined yet.
| Action | What it does |
|---|---|
| Resend | Sends a fresh link for the same invite. Use it when the email did not arrive or the invite expired. |
| Revoke | Cancels the invite. The link stops working, and you cannot undo it. Send a new invite if you change your mind. |
An invite that passed its 7 days shows the status Expired. Resend gives it a fresh link. You see Resend only for invites you may reissue. You cannot resend an invite for a role that has permissions you do not hold.
Change someone's role
- Find the person in the People list.
- Open the role control on their row.
- Pick the new role.
The new role replaces the old one. A promotion swaps the role. It never adds a second role. The change applies right away, including for people who are signed in now.
Member is the usual starting role. Start narrow and move someone up later, rather than giving Org Admin widely. See Roles and permissions for every role.
People can also belong to teams, shown on the same row. You manage teams under Settings → People → Teams, not when you invite someone.
Remove a member
Removing a person cuts their access to the organization right away. The row menu on their row has Remove from organization. It opens a four-step flow:
- What happens. Shows what they own, how many of their connections will be deleted, which API tokens and AI client sign-ins will be revoked, and which teams and roles they leave. Choose Start.
- Hand over. Under Give everything to, pick one person or team. Everything they own follows that choice: toolboxes, templates and custom connectors. On any row you can instead choose Someone else… or delete the item. Giving something to a team makes the team's admin its owner and lets the whole team use and edit it. Choose Next.
- Replace connections. Elaichi always deletes their connections. For each connection, pick another connection of the same app, so the toolboxes that used it keep working. Or choose Leave tools broken. Choose Next.
- Confirm. Read the summary, then choose Remove followed by the person's first name, such as Remove Priya.
Synthetic tools go with their author. They cannot be shared or transferred, so you only confirm the ones that another person's toolbox uses.
You will know it worked when the person leaves the People list.
You cannot undo a removal. Elaichi may ask you to confirm that it is you.
If a person owns a very large number of items, the first Remove may finish only part of the work. Elaichi keeps the work it did, the person stays a member, and the button changes to Continue removing. Choose it to finish.
You cannot remove yourself from the People list. You cannot remove or demote the last Org Owner until someone else is an Owner. You cannot remove a person whose role has permissions you do not hold. Their Remove from organization item is greyed out.
For the full transfer flow outside a removal, see Transfer and offboard.
What to know
- Every organization keeps at least one Org Owner.
- People who join by verified domain or SCIM with no group mapping get Member unless you set another default.
- After someone joins, add them to a team under Teams, so shared connections and toolbox shares reach them as a group.