> 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/invite-by-email.md).

# Invite users by email

Invite a specific person and select the team they should join.

**Before you start:** use an account allowed to manage membership, choose the intended team, and check that the published app is ready for the recipient.

## Send an invitation

1. Open **Users → Users**.
2. Select **Invite Member**.
3. In **Invite with Email**, enter the recipient's email.
4. Open the team selector and choose the appropriate team. Review Administrator, Editor, and Read Only before choosing.
5. Check the email and team, then select **Send Invite**.

![Invite members dialog with separate email and link invitation controls](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FXYcixizdTkrBuE9U2wHP%2F02-invitations.png?alt=media)

The screenshot shows Administrator selected. This is an example of the current selection, not a recommendation for every invitation.

## Invitation email appearance

Free projects use the standard built-in invitation email template. Custom built-in email templates are not available on the Free plan.

## Verify the result

Ask your test recipient to complete the invitation flow. Confirm that the resulting user appears in the Users list with the intended team and can open the published app.

The dialog's unpublished-changes warning means non-builder users will see the published version. Publish the intended app version through your normal release process before comparing their experience with a new builder change.

## Troubleshooting

If an invitation is missing, check the email spelling and the recipient's spam or quarantine folders. Confirm that they are opening the intended app with the invited account before changing permissions.

If sign-in works but access is incorrect, use Test access before publishing.


---

# 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/invite-by-email.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.