> ## Documentation Index
> Fetch the complete documentation index at: https://docs.byterover.dev/llms.txt
> Use this file to discover all available pages before exploring further.
# Team
> Invite teammates and manage access to shared ByteRover spaces.
A team controls who can use shared ByteRover memory, who can manage the workspace, and who can create or share team spaces.
Use team settings when you need to switch teams, invite teammates, change roles, manage billing, or review pending invitations.
## Team surfaces
ByteRover Desktop has four team surfaces.
| Surface | Use it for |
| - | - |
| **Team selector** | Switch the active team, create a new team, or open team management. |
| **General** | Edit the team name and logo, review the owner, leave the team, or delete the team when allowed. |
| **Members** | Invite members, change roles, remove members, resend invites, and revoke pending invites. |
| **Billing** | View the plan, manage seats, open the billing portal, or update payment. Billing is Owner-only. |
## Select the team
Open ByteRover Desktop and choose the team from the team selector.
The selected team controls which **Private** and **Team space** sections you see in the sidebar. When you switch teams, Desktop switches the visible spaces too.
## Open Members
Go to **Members** to manage the roster.
Use search when the roster is long.
## Invite a teammate
Select **Invite member**, enter the teammate's email address, then choose a role.
You can assign these roles during invite:
* **Viewer** - read-only access to team memory.
* **Member** - can add and view memory.
* **Admin** - can manage members and memory.
Owner is not a normal invite role. Ownership is transferred separately by an existing Owner.
## Manage members
From the Members page, Owners and Admins can:
* change a member's role
* remove a member from the team
* resend or revoke pending invitations
* review how many seats are still available
Only Owners can transfer ownership.
## Manage team settings
Open **General** when you need to manage the team itself.
| Setting | Who can use it |
| - | - |
| Team logo | Owner or Admin |
| Team name | Owner or Admin |
| Owner row | Everyone can view |
| Leave team | Admin, Member, or Viewer |
| Delete team | Owner only, and not for the default team |
Leaving a team removes your access to that team's spaces and memory. Deleting a team permanently deletes the workspace, its spaces, and memberships.
## Manage billing
Open **Billing** to review the current plan and seats.
Billing is Owner-only. If someone else owns the team, ask that Owner to manage the plan or payment method.
Owners can:
* open the billing portal
* manage seats on a paid plan
* resume a scheduled cancellation
* update payment when a payment is past due
* start checkout for a paid plan
## Role permissions
Use the smallest role that gives the teammate what they need.
| Role | Permission |
| - | - |
| **Owner** | Full control of the team, billing, and every space inside it. Transferring ownership is itself a privileged action. |
| **Admin** | Runs the team day to day. Admin is identical to Owner except for billing access and the two team-destroying actions: delete team and transfer ownership. |
| **Member** | Uses the team's spaces: reads memories and writes new contexts. Cannot manage members, billing, or sharing. |
| **Viewer** | Read-only seat. Can see the team and read space contents; cannot write or share. |
Review permissions when a teammate changes projects or no longer needs access to a shared memory space.
## Team spaces
Team spaces make memory reusable across the group.
Team roles affect space behavior:
* Owners and Admins can create team spaces.
* Members can read and write memory in spaces they can access.
* Viewers can read memory only.
* Billing access stays Owner-only, even for Admins.
When a teammate works inside a team space, their connected agent can query and record according to that teammate's team role and the space access you grant.
## Next steps
Manage access for a specific memory space.
Start using shared memory from inside your agent.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.