> For the complete documentation index, see [llms.txt](https://docs.spreo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spreo.io/management/manage-teams.md).

# Manage Teams

Teams are groupings of people and boards. The number of Teams you can have is determined by your Billing (Starter = 1 team, all other plans = Unlimited).

Admins and Owners can manage the Teams in an Account.

Each Member should belong to at least one team.

<figure><img src="/files/bJpy8qAc25Y0OPxPxJK0" alt=""><figcaption><p>Here, UX Product Planning has 6 members</p></figcaption></figure>

#### Create a new team

Use the Manage Team screen to create or delete teams for your organization account:

<figure><img src="/files/qzbYEwLBx9X1UCb8FVTI" alt=""><figcaption></figcaption></figure>

* Teams can have as many members as you like (limited by your plan)
* You can drag and drop members from one team to another. Hold shift to copy someone into a new team without leaving the other.
* Members can be in multiple teams.
* To remove members from a team, click on your team to 'open' it and use the 3-dot menu.

#### Delete a Team

* Deleting a Team will immediately archive all boards in that team and remove the members.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.spreo.io/management/manage-teams.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.