Skip to content

Invite and manage people

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

Where to find it: Settings → People → Members

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 a pre-assigned role. The role you select on the invite.
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 and your domain settings under Settings → Organization / Settings → SSO.

Invite someone

  1. Open Settings → People → Members.
  2. Choose Invite member.
  3. Enter their exact work email — the activation link is bound to that address.
  4. Select one role (built-in or custom). Everyone holds exactly one role — it is the whole of what they can do.
  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 role 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 role

  1. Find the person in the People list.
  2. Open the role control on their row.
  3. Pick the new role. It replaces the one they had — a promotion swaps the role, it never stacks a second one on top. Changes apply immediately, including to people who are already signed in.

Member is the usual default for new joiners. Prefer starting narrow and moving someone up a tier later rather than assigning Org Admin broadly. See Roles and permissions for the full catalog.

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

Remove a member

Removing someone immediately cuts their access to the organization. Remove from organization walks you through four short steps:

  1. What happens. How many things they own, how many connections will be deleted, which API tokens and AI client logins are revoked, and which teams and roles they leave.
  2. Hand over. Pick one person or team under Give everything to. Every toolbox, template, automation, dashboard, collection, knowledge base, app and custom connector follows that choice, unless you pick Someone else or Delete it on its row. Giving something to a team makes the team’s admin its owner and lets the whole team use and edit it.
  3. Replace connections. Their connections are always deleted. Pick another connection of the same app for each one, so the toolboxes and automations that used it keep working, or leave those tools broken.
  4. Confirm. Read the summary and select Remove.

Synthetic tools go with their author. They can’t be shared or transferred, so you only confirm the ones somebody else’s toolbox uses.

If they own a very large estate, the first Remove may finish only part of it. The work done is kept, the member stays, and Continue removing finishes it.

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.

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.