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

# Create and manage a team

Setting up and managing teams

Create a named team to organize users with shared permissions or properties.

## Create a team

1. Open **Users** in the builder navigation.
2. Select the **Teams** tab.
3. Select **Add Team**.
4. Enter a **Team Name**, such as Customer Support.
5. Select **Create**.
6. Review the resulting team's settings before assigning users.

The creation dialog describes teams as a way to group users, grant permissions, and assign properties. Creating a named team does not by itself document which actions that team should be allowed to perform.

## Assign people and properties

Select the intended team when [inviting a user](/access-and-sharing/members-users-and-groups/invite-by-email.md) or [creating an invitation link](/access-and-sharing/members-users-and-groups/invite-with-a-link.md). Review existing membership before changing assignments.

Use **Add Property** on the Teams tab when the group needs a shared attribute. Keep the meaning and type consistent with the [user and team property design](/access-and-sharing/members-users-and-groups/user-and-team-properties.md).

## Review team permissions

Document expected access to the builder, settings, membership management, pages, and data actions. Use the controls available for your app version, then verify the result with [representative test accounts](/access-and-sharing/overview/test-access.md).

### Classic builder reference

Older team screens group permissions into Project Permissions and Page Permissions. Their page choices include Full Access, Read-only, Custom Access, and No Access. These labels describe the Classic interface and may differ from your current builder.

For Classic conditional data actions, see [conditional add, edit, and delete](/classic-app-builder/design-and-structure/components-visibility/conditional-add-edit-and-delete.md).

## Video: Classic team setup

This existing video shows the earlier team-management interface. Use the current navigation steps above when working in the current builder.

{% embed url="<https://www.youtube.com/watch?v=lUv_wfNfKR8>" %}


---

# 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.jetadmin.io/access-and-sharing/teams-and-roles/create-and-manage-a-team.md?ask=<question>&goal=<user_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.