# Teams

Teams allow you to manage user access at scale. By creating a specific team, consisting of multiple members, you can grant or remove their access to spaces or collections. Read more about [permissions and inheritance](https://gitbook.com/docs/collaboration/member-management/permissions-and-inheritance).

### Creating and managing teams

You can create, edit, and remove teams in the **Teams** section of your organization settings. 

To find this, click on settings icon in the bottom of your window. Choose organization settings for your desired organization, then click the Teams option in the sidebar.

On this page, you can view and search your current teams, or click one to open the team details page and see more information about it and its members. 

### Managing team members

You can manage team members in two ways:

1. Click on a specific member in **Members & permissions** to open their member page, and select the **Teams** tab. Click the vertical ellipsis and you can remove them from the team immediately, or choose **Manage team.**
2. In the **Teams** section, click on the number of members in the list to open the team details page.  You can then use multi-select on the member list to select and remove team members or add more with the button at the top.

### Team owners

Team owners (available only in Enterprise plans) allow you to hand over management of a specific team to a selected member. Team owners can add and remove members from the team they are an owner of by clicking on the organization settings, then teams. They will not have access to any other organization settings, including managing other teams. 


---

# Agent Instructions: 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:

```
GET https://gitbook.com/docs/collaboration/member-management/teams.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.