Team

A team lets several accounts work with the same gateways. You move a gateway into the team from its row on the Gateways page; members then see it on their Gateways → Team tab. A gateway lives on exactly one team at a time — moving it in takes it off your personal list. The Team page manages the team itself: members, roles, invites, and billing.

Creating a team requires the Team plan. Joining one does not — any approved account can be invited.

Plan caps

How many teams you can own comes from your plan tier, and each team carries its own tier-derived caps — gateways, edge relays, custom domains, verified apexes. Caps are hard: at a cap, the next create is refused (a team already over a lowered cap keeps what it has, but can't add more).

Creating a team

+ Create team on the Team list names the team (with an optional description). A freshly created team is Inactive — nothing can be moved into it — until you Activate team, which needs credit in one of your billing profiles. Add credit first if the activation fails.

Roles

Every member has one of five roles, highest authority first:

Role	Notes
owner	Full control, including deleting the team. A team always keeps at least one owner, and an owner cannot be removed by others.
manager	Can manage members and invites, like an owner, but cannot assign the owner role.
member	Works with shared gateways.
viewer	Read-mostly access. The default role for new invites.
guest	The most limited role.

Only owners and managers can add or remove members, change roles, and manage invites. Members below owner can always Leave a team themselves.

Adding members

Two ways, both under the team's card:

• Add by GitHub username. Start typing and the field suggests matching GitHub accounts — pick one (matching is case-insensitive, so any capitalization of the login finds the same person) and a role. If that person already has a Burrowee account they join immediately; if not, the invite is recorded as pending sign-in and they join automatically the first time they sign in.
• Generate invite link. Pick a role and click Generate invite link — the link is copied to your clipboard. Send it to anyone; opening it signs them in (GitHub OAuth) and joins them at that role. Pending invites of both kinds are listed below, where you can re-copy a link or Revoke it.

Managing members

The team card has two tabs: Members and, for owners only, Billing (see Billing → Team billing).

The member list shows each person's GitHub login, email, and join date. Owners and managers can change anyone's role with the inline dropdown — except demoting the last owner, which is refused — and Remove any non-owner member.

An owner can Edit the team's name and description, or Delete team from the card header (with a confirm). A team with gateways or edge relays attached cannot be deleted — remove those first. Gateways moved off the team return to their owner's personal account; they are never deleted with the team.