> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trynito.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Teams

> Shared organizations on Team plans: seats, roles, nested teams.

Team plans give a group one shared organization with its own billing, seats, and members. Open **Organizations** in the main navigation, or [app.trynito.ai/organizations](https://app.trynito.ai/organizations).

Team Plus, Team Advanced, and Team Max match the individual plans feature for feature, billed per seat with a five-seat minimum. Prices: [Teams](/plans/teams).

## Create a Team

1. From the pricing page, choose **Set up your team**.
2. Name the team.
3. Pick a Team plan and the number of seats on the Billing page that opens.

Your personal organization stays alongside the team. The organization picker in the account menu switches between them.

## Seats

**Members and seats** shows active members and the seat limit.

* **Adding seats** takes effect immediately, prorated for the rest of the billing period.
* **Removing seats** takes effect at the end of the billing period. Owners can cancel the scheduled decrease before renewal.

## Roles

| Role | Can do |
| :- | :- |
| **Owner** | Everything below, plus billing and role changes. The last owner cannot be demoted or disabled. |
| **Admin** | Change roles; disable members; create and revoke API keys; create teams. |
| **Member** | Use the organization's models, plan, and allowance; see the member list. |

Disabling a member removes them from every nested team.

## Nested Teams

Owners and admins create teams inside the organization and assign members to one or more. Teams group people for collaboration and sharing; they use no extra seats and grant no access on their own. Names are unique within an organization.

## Plan and Usage

Plans and allowances belong to the organization. A request made while a team organization is selected draws on the team's plan; your personal organization keeps its own. API keys are organization-scoped too. See [Checking Usage](/plans/checking-usage).

## Next

<CardGroup cols={2}>
  <Card title="Team Plans" icon="tags" href="/plans/teams">
    Prices and seats.
  </Card>

  <Card title="Billing" icon="money-bill" href="/plans/billing">
    Subscription and invoices.
  </Card>

  <Card title="Developer Console" icon="terminal" href="/web-app/developer-console">
    Organization API keys.
  </Card>

  <Card title="Sharing" icon="link" href="/web-app/sharing">
    Encrypted links for teammates.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.