> 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 Create, fill and delete the teams in your organization. Teams are groupings of people and boards. The number of Teams you can have is determined by your plan: the Team and Enterprise plans have unlimited teams, and the legacy Starter plan has 1 team. Admins and Owners can manage the Teams in an Account. Each Member should belong to at least one team.

#### Create a new team Use the Manage Team screen to create or delete teams for your organization account:

* Teams can have as many members as you like (limited by your plan) * Open a team and use 'Add People' to add members to it. People stay in their other teams. * 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 removes its members from the team. Its boards are kept and are listed as 'Not in a team' in Manage Boards. Move them into another team to use them again. * You cannot delete your last team. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.spreo.io/management/manage-teams.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.