Manage team seats

Before you begin

• An enabled account service and eligible paid team scope.
• The intended team Owner account for invitations, member removal and plan management.
• The invitee's correct email and space for active members plus pending unexpired invitations.

Follow the steps

1. Confirm the team and your authority

   Open the intended team under the correct signed-in identity when available. Check that you are its Owner before trying to invite/remove members.

   Checkpoint: The selected team, owner identity and seat allocation are current; ordinary membership grants no owner action.

2. Count used and reserved seats

   Read active members and pending unexpired invitations together. The owner occupies a seat; pending invitations reserve capacity.

   Checkpoint: There is capacity for the intended invitation, including reservations already in progress.

3. Review and send one invitation

   Check the destination email carefully and submit once. Read the resulting invitation record. The launch design uses a single-use invitation with seven-day expiry.

   Checkpoint: A recorded invitation/reserved seat is distinct from delivered email and accepted membership.

4. Accept using the matching verified identity

   The invitee signs in with the exact verified email targeted by the invitation and accepts the current unexpired invitation.

   Checkpoint: The server confirms membership in the intended team; a forwarded link or mismatched account does not grant access.

5. Recheck the team after changes

   For delivery trouble, inspect the existing invite before resending. Cancel unwanted pending invitations or remove a Member only after reviewing the target.

   Checkpoint: The authoritative member/invitation list confirms the change and corresponding capacity, rather than a local optimistic count.

6. Review billing scope before future work

   Each member selects the team scope before a new run. Removal blocks future team admission, while dispatched work retains its original attribution and must finish/reconcile.

   Checkpoint: Membership changes do not transfer private local history, cancel committed effects or silently move costs to a personal wallet.

Check the result

• The team record confirms the intended invitation/membership and accurate active-plus-reserved capacity.
• Team ownership is a billing/authorization scope, not shared access to members' prompts, files or local projects.

If something goes wrong

• The invitee is signed into another email or the invite expired.

  Use the matching verified identity or have the authorized owner review the old invitation and create a new eligible one. Do not bypass identity checks.

  Resume from: Current unexpired invitation and matching account.

• Delivery or submit response is uncertain.

  Reread the existing invitation/team list. Delivery retry reuses the invite; it is not a second seat reservation.

  Resume from: Known original invitation state.

• The last Owner wants to leave or transfer ownership.

  Use the support-assisted audited ownership process. An ordinary leave/remove action cannot remove the last Owner.

  Resume from: Authorized ownership decision before membership change.

• A downgrade has fewer seats than members plus pending invites.

  Review and resolve capacity deliberately before scheduling the downgrade; do not silently evict members.

  Resume from: Capacity fits the target plan.

Continue with a related guide

• Account service availability
• Personal and team wallets
• Plan timing and capacity
• Ownership or invitation help