> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/collaborate/member-management/teams.md). # Teams Learn how to organize Organization members and nests into teams. In a large Organization, not everyone needs access to every nest. Teams limit a set of nests to a specific group of members. Each team sees and manages only its own nests. This keeps projects and client engagements separate within one Organization. You manage teams on your **Organizations** page. You must be an Organization **Owner** or **Admin** to create or manage teams. ### Create A Team 1. **Open your Organization.** Select the user menu in the top right, then select **Organizations**. Select the Organization where you want to create a team. 2. Select **Teams**, then select **New Team**. 3. Enter a name and **Create**. You become the team's **Owner** automatically. The team appears in the list with its member count, number of owned nests, and delete option.

Teams page showing the New Team button and a list of existing teams. — Create and manage teams from the Teams page.

### Add Members You can add only people who belong to your Organization. Invite them first, then wait for them to accept. See [Invite members to your organization](/collaborate/invite-your-team.md). By default, team members keep their Organization role. You can assign a team-specific role instead. Team **Owners** and **Admins** can access the team's nests and manage its members and settings. Team **Users** can access the team's nests only. To become a team **Owner** or **Admin**, you must already be an Organization **Owner** or **Admin**. For definitions, see [Roles](/collaborate/member-management/roles.md). To add members to a team: 1. Select the newly created team. 2. Select **Add Members.** Select members from the list and close. Team members do not need to accept an invite to join a team. Use the search bar to filter to team members and select **Name** to rename the team.

Team details page showing the Add Members button and the member list. — Add organization members from the team details page.

### Give A Team A Nest You need **Admin** access to assign a specific nest to a team. 1. On the nest's **Settings → Access,** select **Add** **Organization**. 2. Select the **Team** instead of the larger Organization. 3. Assign ownership. Everyone on the team can then access the nest. This is the same **Access** panel used for all nest access. See [Share](/collaborate/sharing-and-access.md).

Nest access settings showing an organization and team selection. — Assign a nest to a team from its access settings.

### Find A Team's Nests Nests you can access appear on the **AutoLit** homepage under **Your Nests**. Use the dropdown to narrow the view to one team.

AutoLit homepage showing the Your Nests team filter dropdown. — Filter Your Nests by team on the AutoLit homepage.

You can also open a team's nests from the **Organizations** page on the Team Management page by selecting the total number of nests.

Team Management page showing a team's nest count. — Select a team's nest count to open its nests.

{% hint style="info" %} Integrations and templates aren't limited to teams. Every integration and Organization template is available to all its teams. See [Integrations](/integrations/install-and-manage-integrations.md) and [Organizational Templates](/account-management/organization-management/organization-settings/organizational-templates.md). {% endhint %} ### See Also


Invite Members	Invite people to your organization.	Invite Your Team
Roles	Understand organization and team role permissions.	Roles
Permissions and Inheritance	Learn how access permissions apply across your organization.	Permissions and Inheritance
Sharing and Access	Share nests with people and organizations.	Sharing and Access

--- # 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.nested-knowledge.com/collaborate/member-management/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.