> For the complete documentation index, see [llms.txt](https://guides.noloco.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.noloco.io/users-and-permissions/sharing-your-app/invite-links.md).
# Invite Links
Create reusable links that let people request access to your app with a set role, optionally limited to your email domain
An invite link lets people join your app without you entering their email addresses one by one. Share it in a team chat, an email or an onboarding doc, and anyone who opens it can request access with the role you chose. You can limit a link to one email domain, so only your colleagues can use it.
Everyone who uses a link still has to confirm their email address before they get in. Requesting access sends them the same invitation email as an [email invite](/users-and-permissions/sharing-your-app.md#invite-users-by-email), and they only get access once they've accepted it.
## Create an invite link
1. Click **Share** in the builder's top navigation bar
2. In **Invite links**, click **Create link**
3. Pick the **Role** that people will get when they join through this link
4. Under **Email restriction**, choose who can use the link:
* **Allow any email address**: anyone who has the link
* **Only allow emails from**: enter a domain, like `@yourdomain.com`, to only accept addresses at that domain
5. Click **Create link**
The new link is copied to your clipboard straight away, ready to paste wherever you want to share it. It also appears under **Your active links**.
You can create as many links as you need. For example, one link for your team as Team Admin, restricted to your company's domain, and another for your clients as User.
{% hint style="info" %}
A domain restriction also accepts subdomains. A link limited to `yourdomain.com` accepts both `name@yourdomain.com` and `name@uk.yourdomain.com`.
{% endhint %}
## Manage your active links
Each link under **Your active links** says who can use it and which role they'll get:
* "Anyone can access as **User**": the link accepts any email address
* "Anyone with **@yourdomain.com** email can access as **Team Admin**": the link only accepts addresses at that domain
* Click **Copy** to copy a link again
* Click the trash icon to delete a link. It stops working straight away
Links don't expire. A link keeps working until you delete it, so delete links you no longer need, and replace any link that's been shared somewhere it shouldn't have been.
Deleting a link doesn't remove the people who already requested access through it. They're pending users with the link's role, and you can find or remove them from the Users tab.
If you delete the role that a link grants, the link shows **a deleted role** instead of the role name and stops working. Delete it and create a new link with another role.
## What the person you invite sees
1. They open the link and land on a **Join** page for your app, styled like your login page
2. They enter their email address and click **Request access**
3. They see **Check your inbox** and receive your app's invitation email
4. They follow the email to set up their account, the same way as anyone you invite by email: by setting a password, or by signing in with Google if you've [turned it on](/settings/login-and-signup/sign-in-options.md#sign-in-with-google)
Until they've set up their account, they're a pending user in your app, like anyone you invite by email. A link for a role that can modify your app only gives builder access once the person has accepted the invitation.
### People who already have an account
If someone who's already a user of your app requests access through a link, they see the same **Check your inbox** message and get an email pointing them to sign in. Their role and access don't change. If they were invited before but haven't accepted yet, they get their invitation email again.
### Messages people might see
| Message | Why | What to do |
| ------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ |
| Only @yourdomain.com email addresses can use this invite link | The link is limited to one domain, and the address is at a different one | Use an address at that domain |
| This invite link needs a work email address | The link grants a role that can modify your app or view and manage all data, and the address is a personal one, like Gmail or Outlook | Use a work email address |
| This invite link is no longer valid | The link, or the role it grants, has been deleted | Ask the person who shared the link for a new one |
| Slow down. Please try again later. | A request limit has been reached (see [Limits](#limits)) | Wait a while and try again |
{% hint style="info" %}
If your app requires [single sign-on (SSO)](/settings/login-and-signup/single-sign-on.md), opening an invite link takes people to your login page instead, the same way your sign-up page does.
{% endhint %}
## Limits
To stop a shared link from being used to send spam, invite links limit how often people can request access through them. These limits apply on every plan.
When a limit is reached, people requesting access through the link see **Slow down. Please try again later.** No invitation is sent, so they need to request access again later.
## Tips
* **Restrict links for your team to your company's domain.** This matters most for roles that can modify your app, since anyone with the link can request that access.
* **Use one link per audience.** Separate links for your team and for each group of clients make it easy to delete one without affecting the others.
* **Turn on live mode first.** People whose role can't modify your app can't log in until [live mode](/settings/general-settings/live-mode.md) is on, even after accepting their invitation.
* **Pending users don't take a seat.** People who request access only count towards your plan once they log in. See [User types](/account/pricing.md#user-types).
## Related guides
* [Sharing Your App](/users-and-permissions/sharing-your-app.md): copy your app's link and invite people by email
* [Open Sign Up](/users-and-permissions/open-sign-up.md): let anyone register without a link
* [User Management](/users-and-permissions/user-management.md): manage pending users from the Users tab
* [Email Settings](/settings/email-settings.md): customize the invitation email people receive
---
# 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://guides.noloco.io/users-and-permissions/sharing-your-app/invite-links.md?ask=&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.
