> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nitsor.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Every page in this documentation carries a `plans` list in its frontmatter and a page-details table naming the plans its content applies to: `All plans`, or a subset of `Community`, `Team` and `Enterprise`. A page limited to some plans also opens with a plan marker naming them.
> Use [Capabilities and limits](/product-status) for capability entitlements and documented availability and limits, and [Plans and billing](/plans-and-billing) for plan pricing and billing policy. Those pages are canonical; do not duplicate their policy values here.
> Reading this documentation grants no product access and no permission. No agent can create or approve a Nitsor release.

# Grant project access

> Give one teammate access to one project at the level their work needs, and know what to do when the project does not let you.

[Team and Enterprise](https://docs.nitsor.com/plans-and-billing.md#compare-plans)

Project access decides what one person can do in one project. A Project admin gives it on the project's **Access** page. Workspace owners and admins hold Project admin on every project through their account role.

## Which setting you are changing

| Right | What it covers | Where it changes |
| - | - | - |
| Workspace role | **Owner**, **Admin**, **Billing** or **Member**. Members work on the projects they are given. | **Team settings**, **Members**, the person's page |
| Project access | **Viewer**, **Contributor**, **Operator** or **Project admin**; each level includes the ones before it. | This page |
| Stage roles | The roles a pipeline's stages ask for. A role applies in every project of the workspace whose pipeline uses it. | **Stage roles** on their grant record |
| Data rights | What they can do beyond their role, such as **Register and retry Sources** or **Manage storage connections**. | **Can also** on their member page |

## Give someone access

1. Open the project, then **Settings**, then **Access**.

2. Select **Add person**.

3. On **Add a person**, choose them in **Person or Agent**, then choose a level in **Access**. Someone who is not on the team joins it by invitation first.

4. Select **Add to project**. **Viewer** is added at once. A higher level asks first, for example **Give Demo member Contributor?**, and you confirm with **Add to project**.

   ![The question Give Demo member Contributor?, shown with sample data, saying Demo member gets Contributor on this project: Works the queue. Review comes from stage roles, with the buttons Cancel and Add to project.](https://mintcdn.com/nitsor/ilaLuTr0xz97kTSH/images/grant-project-access-confirm.png?fit=max\&auto=format\&n=ilaLuTr0xz97kTSH\&q=85\&s=69f49fe308e1b7bd733e4655fe5fdba7)

   *Shown with sample data.*

5. Their grant record opens with the toast **Added to project**. It lists **Access**, **Stage roles**, **Qualifications**, **Can also** and **Added**. A workspace owner or admin also sees **Organisation**.

6. A workspace owner or admin gives stage roles. If the project's pipeline asks for one, they select it under **Stage roles** and confirm with **Give role**. If your workspace role is **Member**, the record shows the person's roles as words, or **None**, with nothing to select. **Qualifications** and **Can also** are read-only here. An owner or admin changes them on the person's member page, which the record links to.

If the person belongs to a vendor organisation, the record also has an **Organisation lead** switch. A lead sees and manages that organisation's people on this project, and their access level stays the same.

To change the level later, pick a new one in the person's row on **Access** and select **Update access**. To take access away, select **Remove from project** on their record, then **Remove access**. Their Tasks in progress go back to Waiting if no other access remains. If the record says only part of the team could be read, use **Remove** in their row on **Access** instead.

## If you cannot give access

Below Project admin, the project has no **Settings** tab. If you open **Access** by its address, it shows the four levels and says **Only a project admin can see who holds access to this project and change it.** There is no **Add person**, and **Add a person** says **Only a project admin can add people to this project.** Someone with no access to the project sees **Page not found** there.

Ask a Project admin on the project, or a workspace owner or admin. To find an owner or admin, open **account owners and admins** on the Access page.

## Next step

Learn what each level allows, or start working once you have access.

> [card] [Roles and provenance](https://docs.nitsor.com/concepts/roles-provenance.md)
>
> See what each project level allows and how it differs from a workspace role.

> [card] [Annotate and review](https://docs.nitsor.com/guides/annotate-and-review.md)
>
> Claim a task from the queue, label it and submit it.

<table aria-label="Page details">
  <tbody>
    <tr><th scope="row">Plans</th><td>Team and Enterprise</td></tr>
    <tr><th scope="row">Last verified</th><td>2026-10-31</td></tr>
  </tbody>
</table>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.