> 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/members-users-and-groups.md).

# Users and invitations

Manage the people who use your app from **Users** in the builder navigation. The Users area includes **Users**, **Teams**, and **Authentication**.

## Choose a task

* [Review membership and user access](/access-and-sharing/members-users-and-groups/security-and-privacy.md) before adding or changing access.
* [Invite users by email](/access-and-sharing/members-users-and-groups/invite-by-email.md) when the invitation has a known recipient.
* [Invite users with a link](/access-and-sharing/members-users-and-groups/invite-with-a-link.md) when joining a selected team through a shared link is appropriate.
* [Import and export users](/access-and-sharing/members-users-and-groups/import-and-export-users.md) to work with user records in files.
* [Add user and team properties](/access-and-sharing/members-users-and-groups/user-and-team-properties.md) for attributes such as department or customer ID.
* [Set up teams and roles](/access-and-sharing/teams-and-roles.md) to organize permissions.

## Before you invite anyone

Choose the team deliberately. The invitation dialog can show **Administrator** as its current selection; do not assume that this is the right role for app users.

Check the published app too. The invitation dialog warns that non-builder users see the published app, so an unpublished change may explain a difference between your builder and their experience.

Adding a user record, sending an invitation, and confirming that someone can sign in are separate checks. After onboarding, test with the intended account using [the access test checklist](/access-and-sharing/overview/test-access.md).


---

# 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/members-users-and-groups.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.