# Invite Links
> Part of the NocoDB documentation (Product docs > Users). Index of all pages: https://nocodb.com/llms.txt. Any docs page is available as Markdown by adding `.md` to its URL.
URL: https://nocodb.com/docs/product/collaboration/invite-links
Last updated: 2026-10-21
Create, share, restrict and delete NocoDB invite links that let people join a project or a workspace.
An invite link is a URL that you can share. Anyone who opens it can join a project, a workspace, a classic app or an app with a role that you select. An email invite is for one address only. An invite link is different: it works for all people who have it, until you delete it.
## Create an Invite Link
For a project, do one of these:
* In the top right corner of the project, click **Share**. Stay on the **Invite team** tab.
* Open the project and go to **Project Settings** → **Invite** → **Members**. Then click **Add Members**.
For a workspace:
1. In the workspace sidebar, click **Members & teams** (**Invite Members** in the Community Edition). The **Workspace Members** page opens.
2. Click **Add Members**.
For a [classic app](/docs/classic-apps/share#invite-people-to-a-classic-app) or an [app](/docs/apps/members-and-teams#share-an-app), click **Share** in its builder.
Below **Invite via private link**:
1. Select the [role](#roles-a-link-can-grant) that people get when they join.
2. Click **Create an invite link**.
NocoDB creates the link and copies it to your clipboard in one step. After the link exists, the button shows **Copy invite link**.
No link is created just because the dialog was opened. A link only exists once you ask for one.
### Roles a link can grant
| Scope | Roles on offer |
| ----------- | -------------------------------------------- |
| Project | Creator, Editor, Commenter, Viewer, App User |
| Workspace | Creator, Editor, Commenter, Viewer |
| Classic app | Editor, Commenter, Read only |
| App | The teams of the app, except **Admin** |
**Owner** is never available, for a project or for a workspace. Roles higher than your role are greyed out.
## Manage Invite Links
A project or workspace can have many links. Each link has its own role and restriction. To open the **Invite links** screen, click the **invite links** count next to the **Invite via private link** heading.
Each row shows the role and the restriction of a link, and who created it. On this screen, you can:
* Click **Copy link** on a row.
* Click the settings icon on a row. The link opens in the [**Edit invite link**](#link-settings) screen.
* Click **Create new link** to add a link.
A row is marked as not working when NocoDB would refuse to redeem it. This happens when the creator no longer holds the role that the link grants, when the link grants a role that links can no longer offer, or when the project went private under a creator who is not the project Owner. A link also stops working when it expires, when it reaches its use limit, or when the app team that it adds people to is deleted. The row shows which case applies. These links stay in the list, and you can still revoke them. To make a link work again, restore the creator's role or the project's default access.
If your role is lower than Creator, you see and manage only the links that you created.
## Link Settings
Open a link from the [**Invite links**](#manage-invite-links) screen. You can change these settings:
| Setting | What it sets |
| ------------------ | ---------------------------------------------------------------------------------------------------------- |
| **Permission** | The role that people get when they join. A change applies to all people who use the link after the change. |
| **Who can access** | **Allow any email address**, or **Only allow emails from** one domain, for example `acme.io`. |
The default for **Who can access** on a new link:
| You signed up with | A new link accepts |
| ----------------------------------- | -------------------------- |
| A work (not personal) email address | Only your own email domain |
| A personal email address | Any email address |
A domain restriction is matched on the address alone, and the match is exact: a link restricted to
`acme.io`
does not accept an address at
`evil-acme.io`
. On NocoDB Cloud the address is verified at sign-up; on Community Edition and self-hosted self-signup nothing verifies it, so treat the restriction as a convenience rather than a security control.
To stop a link, open it and click **Delete link**. The link stops working immediately for all people who have the URL. People who already joined through the link keep their access.
[**Create new link**](#manage-invite-links) opens the same controls with the title **New invite link**. This screen does not have the **Delete link** button.
## Joining Through a Link
When you open an invite link, the page shows the name of the project, workspace or classic app and the role. An app link shows the name of the app and the team that you join. If the link has a domain restriction, the page also shows it.
| If | The page shows |
| ------------------------------------------------------ | ------------------------------------------------------------------------- |
| You are signed out | **Create an account to join** or **Sign in to join** |
| You are signed in | **Join now** |
| Your address does not match the domain restriction | A message about the restriction, and **Sign in with a different account** |
| You already have the role of the link or a higher role | The project or workspace. You do not have to join. |
A [deleted](#link-settings) link shows that it is deleted. It does not show the project or workspace.
Redeeming a link never lowers access. If you already hold a higher role than the link grants, your existing role is kept.
### What a project link grants
A project link gives access to that project only. NocoDB adds the person to the workspace of the project with **No Access**. The person sees that one project and nothing else in the workspace. A person who already has a workspace role keeps it.
On paid plans, NocoDB gives a role that uses a seat only if the plan has a free seat. If no seat is free, the person joins as **Viewer**. **Viewer** does not use a seat.
### What a classic app or app link grants
A classic app link gives access to that classic app only. An app link adds the person to one team of that app. In both cases the person gets no role in the project and does not see its tables or views.
## Invite Links on a Private Project
On a [private project](/docs/product/projects/private-project), only the project **Owner** can create an invite link. Links that other people created stop working while the project is private. They work again if you set the project back to default access.
## Best Practice
* When you invite colleagues, restrict the link to your company domain. Leave a link open only when you want all people with the URL to join.
* Create a separate link for each role. Do not change the role of a link that people already have.
* [Delete](#link-settings) links that you do not need. A link stays valid until you delete it.
* To add one specific person, use an email invite, not a link.
## Availability
* To create an invite link, you need the **Editor** role or higher. The role of a link cannot be higher than [your own role](#roles-a-link-can-grant). Thus, you cannot give more access than you have.
---
## Related pages
- [Workspace Collaboration](https://nocodb.com/docs/product/collaboration/workspace-collaboration.md): Invite members and teams to a NocoDB workspace, change their workspace roles, and remove them.
- [Project Collaboration](https://nocodb.com/docs/product/collaboration/project-collaboration.md): Invite members and teams to a NocoDB project, change their project roles, and remove or block their access.