# 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-03

Create, share, restrict and delete NocoDB invite links that let people join a base or a workspace.

An invite link is a URL that you can share. Anyone who opens it can join a base or a workspace 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 base, do one of these:

* In the top right corner of the base, click **Share**. Stay on the **Invite team** tab.
* Open the base and go to **Base Settings** → **Invite** → **Members**. Then click **Add Members**.

For a workspace:

1. In the workspace sidebar, click **Invite Members**. The **Members** page opens.
2. Click **Add Members**.

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**.

<img alt="The Invite team tab with the Invite via private link block" src={__img0} placeholder="blur" />

<Callout type="info">
  No link is created just because the dialog was opened. A link only exists once you ask for one.
</Callout>

### Roles a link can grant

| Scope     | Roles on offer                                        |
| --------- | ----------------------------------------------------- |
| Base      | Creator, Editor, Commenter, Viewer, App User, Inherit |
| Workspace | Creator, Editor, Commenter, Viewer                    |

**Owner** is never available, for a base or for a workspace. Roles higher than your role are greyed out.

<img alt="The roles an invite link can grant" src={__img1} placeholder="blur" />

## Manage Invite Links

A base 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.

<img alt="The invite links count on the Invite team tab" src={__img2} placeholder="blur" />

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.

<img alt="The Invite links screen" src={__img3} placeholder="blur" />

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          |

<Callout type="info">
  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.
</Callout>

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.

<img alt="The Edit invite link screen" src={__img4} placeholder="blur" />

[**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.

<img alt="The New invite link screen" src={__img5} placeholder="blur" />

## Joining Through a Link

When you open an invite link, the page shows the name of the base or workspace and the role. 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 base or workspace. You do not have to join.                           |

A [deleted](#link-settings) link shows that it is deleted. It does not show the base or workspace.

<img alt="The join page for a base invite link" src={__img6} placeholder="blur" />

<Callout type="info">
  Redeeming a link never lowers access. If you already hold a higher role than the link grants, your existing role is kept.
</Callout>

### What a base link grants

A base link gives access to that base only. NocoDB adds the person to the workspace of the base with **No Access**. The person sees that one base 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.

## Invite Links on a Private Base

On a [private base](/docs/product/bases/private-base), only the base **Owner** can create an invite link. Links that other people created stop working while the base is private. They work again if you set the base 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.
- [Base Collaboration](https://nocodb.com/docs/product/collaboration/base-collaboration.md): Invite members and teams to a NocoDB base, change their base roles, and remove or block their access.