> ## Documentation Index
> Fetch the complete documentation index at: https://docs.voxworks.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Inviting & Managing Members

> How to invite people to a team, manage pending invitations, accept an invite as a new user, change roles, remove members, leave a team, and transfer ownership.

## Overview

Every team has its own membership list, managed from **Settings → Members**. From here you can invite new people, track invitations that haven't been accepted yet, change what role an existing member holds, remove someone from the team, and — if you're the primary owner — hand ownership of the team to someone else.

The page is built from two cards:

* **Team Members** — everyone with active access to the team, plus a search box and the **Invite Members** button.
* **Pending Invites** — invitations that have been sent but not yet accepted.

Teams use two roles, **Owner** and **Member**. What each role can do — including the difference between an Owner and the team's single **primary owner** — is covered in [Roles & Permissions](/team/roles-permissions). This page focuses on the day-to-day mechanics of managing who's on the team.

***

## Inviting Members

Click **Invite Members** (top-right of the Team Members card) to open the **Invite Members to your Team** dialog. By default, both Owners and Members can send invites — invite access isn't restricted to Owners alone.

Each invite row has two fields:

| Field     | Description                                                                                   |
| --------- | --------------------------------------------------------------------------------------------- |
| **Email** | The invitee's email address. Placeholder text: *[member@email.com](mailto:member@email.com)*. |
| **Role**  | The role they'll hold once they accept. Defaults to **Member**.                               |

The roles available in the selector depend on your own role: an Owner can invite someone as either **Owner** or **Member**, while a Member can only invite new people as **Member** — you can't invite someone into a more senior role than your own.

Click **Add another one** to queue up to **5 invites** in a single batch — this is the only fixed limit on the dialog. Each row beyond the first has a remove (**×**) button; the last remaining row can't be removed. The same email address can't appear twice in one batch, and you can't invite an address that already has a pending invitation to the team.

Submit with **Send Invites**. While it's processing you'll see *Inviting members...*, followed by a success toast once the emails are queued. Recipients receive an email invitation to join; accepting it is covered in [The /join experience](#the-join-experience) below.

<Warning>
  If you invite someone with the **Owner** role, accepting the invite makes them the team's new **primary owner** immediately and automatically — see [Owner Invites and Ownership Transfer](#owner-invites-and-ownership-transfer).
</Warning>

***

## Pending Invitations

The **Pending Invites** card lists every invitation that's been sent but not yet accepted, with a **Search Invitations** box above the table. Each row shows:

| Column         | Description                                                                             |
| -------------- | --------------------------------------------------------------------------------------- |
| **Email**      | The invited address.                                                                    |
| **Role**       | The role the invite will grant on acceptance.                                           |
| **Invited at** | When the invite was sent.                                                               |
| **Expires at** | When the invite stops working — 7 days after it was sent, or after it was last renewed. |
| **Status**     | **Active** or **Expired**, based on the expiry date above.                              |

Only members with role-management permission — normally Owners — see an actions menu (**⋮**) on each row, with up to three options:

* **Update Invitation** — change the role the invite will grant. You're offered the same role-selection rules as the invite dialog (based on your own seniority), and the new role must differ from the invite's current one.
* **Renew Invitation** — only shown once an invite has expired. Extends the expiry to 7 days from the moment you renew it, without changing the invite link or role.
* **Remove Invitation** — deletes the invite outright. The invited person will no longer be able to join using that link.

Anyone who can invite members (Owners and Members alike) can send invites, but only Owners can edit, renew, or remove a *pending* invite after it's sent.

***

## The /join Experience

Invitation emails link to a join page carrying an invite token. What the invitee sees depends on their sign-in state:

* **Not signed in, or no account yet** — they're sent to sign up (or sign in) first. The invite token and email travel with them through that flow, so they land back on the invite screen once they've authenticated.
* **Already signed in and already on the team** — they're redirected straight to the team's home page; there's nothing to accept.
* **Invalid or expired token** — they see an **Invite not found or expired** screen: *"The invite you are looking for is either expired or does not exist. Please contact the team owner to renew the invite."* with a **Back to Home** button. An Owner can send a fresh invite, or renew the existing one from the Pending Invites table if it only expired.
* **Valid invite, signed in** — they see **Accept Invitation to join `{team name}`** (with the team's logo, if it has one), a short description, and a **Continue as `{their email}`** button. Clicking it shows *Joining team...* while the invite is accepted, then redirects them straight into the team.

Below the accept button, a **Sign in with a different account** option signs the invitee out and lets them switch accounts first if the invite was meant for a different email address than the one they're currently signed in with.

Accepting the invite creates their membership with the role the invite specified, and removes the invitation from the Pending Invites list.

***

## Owner Invites and Ownership Transfer

Sending an invite with the **Owner** role does more than grant the Owner role on acceptance — it hands over **primary ownership** of the team the instant the invite is accepted, automatically and without any additional confirmation step. This applies no matter which Owner sent the invite, not only the current primary owner.

When this happens:

* The person accepting the invite becomes the team's new primary owner and is given the Owner role.
* The previous primary owner keeps their Owner role and everything that comes with it, but is no longer flagged as *primary* owner — they lose primary-owner-only abilities such as deleting the team (see [Deleting an Account or Team](/account/deletion)).

Because this transfer happens automatically on acceptance, only invite someone as Owner if you intend for them to become the team's primary owner. If you want to add another Owner-level member **without** handing over primary ownership, that isn't available through the invite role — every Owner-role invite results in a primary-ownership transfer once accepted.

### Transferring ownership of an existing member instead

If the person you want to make primary owner is already on the team, use **Transfer Ownership** from their row instead of sending a new invite. This action only appears on the current primary owner's screen (or for a super admin) — other Owners can't initiate a transfer this way.

1. From the target member's **⋮** menu, choose **Transfer Ownership**.
2. Verify your identity: click **Send Verification Code**, enter the 6-digit code sent to your email, and click **Verify Code**. Use **Request New Code** if it doesn't arrive or expires.
3. Read the warning — *"You are transferring ownership of the selected team to `{member}`."* — and confirm.
4. Click **Transfer Ownership** (shown as *Transferring ownership...* while it processes).

The selected member becomes the new primary owner immediately; you keep your own Owner-role membership but lose primary-owner status, the same outcome as accepting an Owner-role invite.

***

## Changing a Member's Role

Each row in the **Team Members** table shows the member's avatar, display name (with a **You** badge on your own row), email, role badge, and join date. A member flagged with the yellow **Primary Owner** tag next to their role badge never shows an actions menu — their role can't be changed or removed from this table.

For anyone else, the **⋮** menu offers **Update Role** if you outrank them (your role must be more senior than theirs) — this is why an Owner can manage a Member, but a Member can't manage another Member or any Owner. Choosing **Update Role** opens **Update Member's Role**: pick a different role from the selector (you can't reselect their current role) and confirm with **Update Role**. The change takes effect immediately.

Your own row never shows an actions menu, even to change your own role — role changes always come from another member acting on you.

***

## Removing a Member

From the same **⋮** menu, **Remove from Account** is available under the same seniority rule as role changes — you must outrank the member you're removing, and the primary owner can never be removed this way.

Confirm in the **You are removing this user** dialog — *"Remove this member from the team. They will no longer have access to the team."* — then click **Remove User from Team**. Removal is immediate: the person loses access to the team straight away and needs a fresh invite to rejoin later.

***

## Leaving a Team

To leave a team you belong to (but don't own), use **Settings → General → Danger Zone → Leave Team**, not the Members page — see [Leaving a Team Instead](/account/deletion#leaving-a-team-instead) for the full steps. The primary owner can't leave their own team; they need to transfer ownership first, using either method described above.

***

## Seat Billing

Your team's membership count and its subscription stay in sync automatically: accepting an invitation increases the account's seat count, and removing a member decreases it. For a plan billed per seat, this keeps what you're charged aligned with how many people are on the team without any manual adjustment on your part; plans that aren't billed per seat are unaffected by team size. See [Subscriptions & Plans](/billing/subscription) for how your plan is billed.

***

## Next Steps

* [Roles & Permissions](/team/roles-permissions) — what Owner and Member can each do, and how primary ownership differs from the Owner role.
* [Team Settings & Notifications](/team/settings) — the rest of the Settings area, including the Danger Zone where members leave a team.
* [Deleting an Account or Team](/account/deletion) — leaving vs. deleting, and what only the primary owner can do.
* [Subscriptions & Plans](/billing/subscription) — how your plan is billed, including per-seat pricing.
