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

# Review and verify teams

> Check submitted teams, verify them or send them back, and edit, unverify or disband a team.

Staff verify a team on **Teams** after its captain submits it. Only verified teams can go in a match or appear on the Player Hub's Teams page.

| Status | What it means | What players see |
| :- | :- | :- |
| **Building** | The captain is putting the team together and can change its name, colour and logo. | **Building** |
| **Pending** | Submitted for review. The captain can't change its name, colour or logo. | **Pending Review** |
| **Verified** | Accepted by staff. Its name, colour and logo stay locked for the captain. | **Verified** |

At any status, players can join and leave a team, up to the team size limit, and the captain or staff can remove them.

## Before you start

* You need access to manage teams. See [How access works](/get-started/access).

## Verify a team

<Steps>
  <Step title="Find the teams waiting for review">
    In the sidebar, select **People** → **Teams**, then the **Pending** tab. Verified teams are on the **Approved** tab. You can also open a team from the Dashboard's **Needs attention** panel, which lists each team ready for review.
  </Step>

  <Step title="Open the team">
    Select the team's row. You see its name, status, colour and creation date, and its roster with the captain and when each member joined. A **Ready for review** bar heads the roster.
  </Step>

  <Step title="Check the roster">
    Check the team against your rules, such as its number of players. Select a member's row for their player details.
  </Step>

  <Step title="Verify or send it back">
    * To accept the team, select **Verify team**, then **Verify**. Its status becomes **Verified**.
    * To return it to the captain, select **Send back**. It goes back to **Building** straight away, with no dialog, so the captain can change it and submit it again.
  </Step>
</Steps>

## Edit a team

Staff can change a team's name, captain and colour at any status. Only the captain can change the logo, while the team is **Building**.

1. Open the team and select **Edit team**.
2. Change the **Team name**, choose a new **Captain** from the members, or pick a new **Team colour**.
3. Select **Save changes**.

A team name is 3 to 15 characters: letters, numbers and spaces. No two teams can share one.

<Warning>
  Renaming a team gives it a new invite code, and the old code stops working. The captain must send the new one to anyone still joining.
</Warning>

## Unverify a team

Open the team, select **More team actions**, the three dots beside **Edit team**, then **Unverify team**, and confirm with **Unverify**. The team goes back to **Building**, and the captain can edit it again.

A match already on the schedule keeps the team. On **Schedule**, the team shows as "(not verified)".

## Remove a member or disband a team

* **Remove a member.** Open the team, select **Remove** on the member's row, then **Remove** again. They can rejoin with a valid invite code. Removing the captain passes captaincy to the member who joined earliest. Removing the last member disbands the team.
* **Disband a team.** Open the team, select **More team actions** → **Disband team**, type `disband` and select **Disband**.

<Warning>
  Disbanding removes every member and deletes the team. It can't be undone. Matches already on the schedule keep the team's name.
</Warning>

## Next steps

<Columns cols={2}>
  <Card title="Plan the schedule" href="/season/schedule">
    Put verified teams into matches.
  </Card>

  <Card title="Open and close sign-ups" href="/season/sign-ups">
    Control when players can create teams.
  </Card>
</Columns>


## Related topics

- [How a season runs](/get-started/how-a-season-runs.md)
- [Open and close sign-ups](/season/sign-ups.md)
- [Plan the schedule](/season/schedule.md)
- [Keep staff notes and ban players](/season/players.md)
- [Glossary](/get-started/glossary.md)


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