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

# User & Role Management

> Who can do what on a project: the three project permission levels, how invitations work, and the different ways you can share your project.

A project has one owner and any number of people invited to it, each holding a certain permission level that decides what they can do.

## The Three Permission Levels

| Level      | What it means                                                                                                       |
| ---------- | ------------------------------------------------------------------------------------------------------------------- |
| **Owner**  | The person who created the project. Manages collaborators and their roles                                           |
| **Editor** | Can work in the project: prompt the agents, edit the CAB, change Tickets, and may perform Build and Test activities |
| **Viewer** | Can see the full project without making any changes to it                                                           |

**Owner is not something you may be granted.** It comes from creating the project. Each project will have only one owner.

## Inviting Someone

You may invite collaborators into your project from two places: From the Projects Dashboard and using the Manage Collaborations icon from the project tools rail.

<Frame caption="Manage Collaboration - Create an Invitation or view the members list to see who already has access">
  <img src="https://mintcdn.com/bluegenai/7waybd6h9m5O59_U/images/Manage-Collaboration-3.gif?s=bb6a9c5994e9a1cfa0e6118752e1e39f" alt="Manage Collaboration" title="Manage Collaboration" width="994" height="670" data-path="images/Manage-Collaboration-3.gif" />
</Frame>

To create an invitation:

1. Set the Permission Type (Viewer or Editor). This may be changed later
2. Enter one or more email addresses
3. Send.

Invitations appear in the ***recipient's*** **Invitations** tab on their dashboard, and in ***your*** **Pending Invites** list until they respond.

<Frame caption="The members list separates people who have accepted from invitations still outstanding.">
  <img src="https://mintcdn.com/bluegenai/NDGsqiI6WIlzZ3zL/images/getting-started/user-role-management-members.png?fit=max&auto=format&n=NDGsqiI6WIlzZ3zL&q=85&s=f9afc6298b8a641ca512f7914958fcde" alt="The members list showing tabs for Active Members and Pending Invites, a search field, and rows showing each member's name, email, date added, and role." width="1533" height="757" data-path="images/getting-started/user-role-management-members.png" />
</Frame>

An invitation can be Accepted, Rejected.  The request may also be withdrawn by the project owner before it is accepted. Someone who has accepted can later leave, or be removed.

Once Accepted, the user will appear in the Active Members tab of the collaboration panel.

<Note>
  When setting Permission Type to Editor, you must choose a billing preference. <br />   Selecting **Owner** means that the user's actions will charge to the Project Owner.<br />   Selecting **Collaborator** will charge the user's activity to their own account's credits.
</Note>

## Other Types of Sharing

These are different mechanisms with different audiences, and it is worth not confusing them.

**Shareable Link Access** is an additional toggle in the collaboration drawer. It creates a special invitation URL lets ANY user of the platform who has an account, is signed in, and has the link **request** access to the project. It does not immediately grant access; someone still approves the request.

**Read-only share links** are available for the CAB. Anyone with the link can open the generated CAB **without signing in at all**. Nothing else in the project becomes visible and nothing is editable.

<Warning>
  A read-only share link needs no account and no approval. Only enable one on an item you are content for anyone holding the URL to read.
</Warning>

## What's the Difference

Permissions are checked wherever an action would alter the project.

A Viewer can open the workspace, read the CAB, and look at Tickets, but the controls that change things are unavailable to them.

Read-only questions are treated separately from changes, so a collaborator may be able to ask the agent about a codebase on a project where they cannot build.

## Your Next Step

<CardGroup cols={2}>
  <Card title="Start a project" icon="rocket" href="/getting-started/quick-start-guide">
    Requirements to deployed application, in one pass.
  </Card>

  <Card title="Find your way around" icon="compass" href="/getting-started/navigation-ui-guide">
    The dashboard, the workspaces, and the four modes.
  </Card>
</CardGroup>


## Related topics

- [Common Workflows by Role](/tips-and-tricks/common-workflows-by-role.md)
- [Weekly release notes](/changelog/weekly-release-notes.md)
- [BlueGenAI Documentation](/index.md)
- [Component Reference](/low-code/servicenow/build-mode/component-reference.md)