> 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/built-in-roles.md).

# Choose a built-in role

The invitation team selector describes three built-in teams. Use these descriptions to choose an initial access level.

| Built-in team | Description shown in the app            | Typical starting point                   |
| ------------- | --------------------------------------- | ---------------------------------------- |
| Administrator | Can build application and modify data   | People responsible for building the app. |
| Editor        | Can modify data in application          | People who work with app data.           |
| Read Only     | Can only view data without modification | People who need to inspect information.  |

![Built-in team selector showing Administrator, Editor, and Read Only](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FXsN1hhEhRcvErfNBSC6F%2F03-role-picker.png?alt=media)

These descriptions are a starting point, not a complete permission matrix for every page, API, workflow, or integration.

## Assign and verify

1. In **Users → Users → Invite Member**, open the team selector.
2. Choose the least access that supports the person's task.
3. Complete the invitation.
4. Test both an allowed action and a denied action using the resulting account.

For a Read Only test user, check that viewing intended records works and that create, update, and delete attempts are denied. For an Editor, verify permitted data changes and check whether builder or administration screens are accessible.

Use [the access test matrix](/access-and-sharing/overview/test-access.md) to record the result. If the observed behavior differs from the intended role, investigate the app's rules and other team assignments before sharing it more widely.


---

# 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 dynamically 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/built-in-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 `build a script that syncs our docs to a CMS` 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.