> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tavus.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Teams
> Share one Tavus account across your organization, with roles that control who can manage members, billing, API keys, and single sign-on.
## Overview
A team lets several people work under one Tavus account. Everyone on the team shares the same plan and usage allowance, and each member keeps their own login and, depending on their role, their own API keys.
Every team has three roles.
| | Admin | Member | Viewer |
| :--------------------------------------------- | :---- | :----- | :----- |
| Use the platform | Yes | Yes | Yes |
| View team members, invitations, and the plan | Yes | Yes | Yes |
| Create and delete their own API keys | Yes | Yes | No |
| Delete another member's API key | Yes | No | No |
| Invite, remove, and change the role of members | Yes | No | No |
| Set up and manage single sign-on | Yes | No | No |
| Change or cancel the plan | Yes | No | No |
Manage your team from **Settings** in the [Tavus Portal](https://maker.tavus.io/dev/settings).
## Leaving a Team
An admin can remove a member, and any member can leave on their own. Both work the same way: the person keeps their login and everything they created, and moves to a new personal account.
Two things stop working at that moment:
* Their API keys are revoked, along with any invitations they had sent that nobody had accepted yet.
* Anything shared with the team rather than owned by them personally, such as team campaigns, stays with the team.
A team always needs at least one admin. The last admin cannot leave, be removed, or be changed to a member or a viewer - promote someone else first.
The member whose email address is on the team's billing account cannot be removed. Contact support if you need to change who that is.
## Next Steps
Let your team sign in to Tavus through your own identity provider.