> 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.md).

# Teams and roles

Use teams to group people with a shared access requirement. Begin with the built-in role descriptions, then review any app-specific permissions.

## Recommended sequence

1. [Choose a built-in role](/access-and-sharing/teams-and-roles/built-in-roles.md) for each audience.
2. [Create a team](/access-and-sharing/teams-and-roles/create-and-manage-a-team.md) when a named group is useful.
3. [Invite users](/access-and-sharing/members-users-and-groups/invite-by-email.md) to the intended team.
4. Add [user or team properties](/access-and-sharing/members-users-and-groups/user-and-team-properties.md) only when an access rule or personalization needs them.
5. [Test access](/access-and-sharing/overview/test-access.md) with representative accounts.

## Design teams around tasks

For a ticket app, a support team might update tickets while a reviewer only reads them. A builder who changes the app needs a different access level from an agent who changes ticket data.

Write down the intended permissions for each team before configuration: pages, records, create/update/delete actions, and builder or administration access. A team name such as Support or Managers is a label; verify the actual permissions behind it.

When a person belongs to more than one team, test their effective access. Do not assume a restrictive team overrides a broader one unless you have verified the behavior in your app.


---

# 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.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.