# Invite and manage a team

Invite members, change roles, transfer ownership, remove access, and leave safely.

Team organisations support invitations, accepted membership, roles, and ownership transfer. Personal
organisations have one fixed owner and do not support team membership.

Owners and admins manage the team. Ownership transfer remains owner-only.

## Invite a member

Open **Organisation settings → Team**, enter the recipient email, and select admin, member, or viewer.
Choose the least privileged role that supports the person's work.

The invitation is email-bound and remains pending until accepted through its join link. Cancel unused
or mistaken invitations rather than leaving access pending indefinitely.

Pending invitations do not count as accepted paid Team members. Grandfathered Team Free organisations
still apply their occupied-seat gate when invitations are created.

## Recipient experience

An existing FeatureGate account signs in before accepting. A new recipient follows the join flow and
completes account verification as required.

The invitation recipient email pre-fills registration. A matching address can follow the verified
invitation path. A changed address must complete normal email-code verification before account creation.

Do not forward an invitation as a general team join link. Organisation invitations are recipient-bound.

## Change a role

Owners and admins can change non-owner roles. Confirm the new role against the permission matrix before
applying it.

Role changes write organisation activity. A direct change to a person's access sends mandatory email
even when they have disabled optional project or billing notifications.

Owner is protected and cannot be assigned through an ordinary role edit. Use ownership transfer.

## Remove a member

Owners and admins can remove non-owner members. Before removal:

1. Identify keys and automation operated by the person.
2. Transfer operational ownership where needed.
3. Revoke shared credentials they could still possess.
4. Confirm billing impact for an accepted Team member.
5. Remove membership and review activity.

Removing console membership does not automatically invalidate every application credential the person
previously copied. Credential lifecycle must be handled separately.

## Transfer ownership

Only the current owner can transfer ownership. The recipient must already be an accepted member.

The recipient becomes owner and the outgoing owner becomes admin in the same transaction. Review
billing, closure, project-transfer, and automation responsibilities before confirming.

Personal organisation ownership cannot transfer. Promote or create a team organisation when ownership
needs to become shared and transferable.

## Leave an organisation

A non-owner member can leave a team organisation when another accepted member remains. Owners, personal
organisation members, and sole members cannot leave.

Self-leave writes activity but does not send a redundant removal email to the departing person. The
remaining organisation retains historical attribution for their actions.

## Billing effects

Paid Team billing counts accepted active members and enforces a three-seat minimum. Removing or leaving
may reduce provider quantity above the minimum; pending invitations do not increase it.

Review the Billing page before a significant membership change. Business and manual billing may need
support coordination.

## Common problems

- **The recipient cannot accept:** confirm the invitation is active and the intended email is used.
- **A role cannot become owner:** complete owner-only transfer instead.
- **The owner cannot leave:** transfer ownership first.
- **A sole member cannot leave:** add and accept another member or use the supported closure path.
- **A removed person's key still works:** revoke the credential separately.

Related pages: [Roles and permissions](/docs/administration/roles-and-permissions),
[Plans and billing](/docs/administration/plans-and-billing), and
[Account settings and security](/docs/administration/account-settings-and-security).