> 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-with-a-link.md).

# Invite users with a link

Create a team-specific invitation link when everyone who receives that link should be able to join the selected team.

**Access behavior:** the invitation dialog states that anyone on the internet with the link can join the selected team. Choose the audience and team before generating or sharing it.

## Create the link

1. Open **Users → Users → Invite Member**.
2. Find **Invite with Link**.
3. Open **Choose Team** and select the intended team.
4. Select **Add Invite Link**.
5. Review the resulting link and its team before copying it to your intended audience.

![Invite with Link area showing Choose Team and Add Invite Link](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FXYcixizdTkrBuE9U2wHP%2F02-invitations.png?alt=media)

For a named recipient, consider [an email invitation](/access-and-sharing/members-users-and-groups/invite-by-email.md) instead. Avoid distributing an Administrator invitation link for ordinary app onboarding.

## Verify the joining experience

Use an intended test account to open the link and complete joining. Confirm the team in the Users list, then test the published app with that account.

Do not assume that a link expires, has a usage limit, or stops working after you change a user's membership. Check the controls available for that link and test its behavior before relying on those properties.

Keep an owner and distribution record for shared links so access reviews include the ways new people can still join.


---

# 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-with-a-link.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.