> ## Documentation Index > Fetch the complete documentation index at: https://to11.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Team > Invite people to your organization, manage the roster, and handle pending invitations. The **Settings → Team** page is where you invite people to your [organization](/docs/platform/organizations), see who's a member, and manage invitations. What each person can do once they join is governed by their [role](/docs/platform/roles-and-permissions). ## Inviting someone Choose **Invite** and fill in the invitation: * **Emails** — one or more addresses (you can paste a list, up to 50 at a time). * **Organization role** — **Admin**, **Developer**, or **Member** (the default). This sets the person's baseline access across the whole organization. * **Note** — an optional message included in the invitation email. * **Workspace and project access** — optionally grant a role on specific [workspaces](/docs/platform/workspaces) or [projects](/docs/platform/projects), on top of their organization role, for finer-grained access. Sending invitations requires the `invites:manage` permission. An invited person joins once they accept the invitation and sign in. See [Authentication](/docs/platform/authentication) for how sign-in works. ## Pending invitations Invitations that haven't been accepted yet are listed under **Pending invites**, with the assigned role, any direct workspace or project access, and when each invitation expires. For each one you can: * **Resend** — send the invitation email again (also useful if it's close to expiring). * **Revoke** — cancel the invitation so its link no longer works. You can also resend every pending invitation at once. Both actions require `invites:manage`. ### How an invitation is accepted An invitee is matched to their invitation by **verified email**: they accept by signing in with an account whose verified email matches the one you invited. If the emails don't match, acceptance is refused. When someone signs in for the first time and their verified email matches one or more pending invitations, those invitations are accepted automatically — so a teammate who already has the right email signs in and lands in your organization. ## Removing someone Open a member's row actions and choose to remove them, then confirm. Removing a member revokes their organization membership along with any workspace and project access, so they immediately lose access to everything in the organization. Two guardrails apply: * You can't remove the **last owner** of the organization — there must always be someone who can administer it. * You can only remove members whose role you outrank or match. An admin can't remove an owner. Removing members requires the `members:manage` permission. ## Next steps Decide what each person can do. How people sign in.