Project members and access

Every project keeps its own list of members, each with an access level that applies inside that project only. This lets a project be shared with specific users at a defined level without changing their global role. Members are managed from the Manage members action in the projects list, which opens the Project members dialog.

Access levels

A project access level is granted per user and per project. It never widens the user's global role — it can only narrow it.

Access level	What the member may do in the project
Developer	Full access to the project's analytical objects: RMD, fact tables, connections, data marts, and project versions
Analyst	Builds data marts from existing elements, creates and edits data marts, and runs SQL scripts for fact tables and data marts. Cannot edit the RMD, fact tables, connections, or versions
Viewer	Read-only access: views project content and generates, views, and copies SQL scripts

Two more project roles appear in the interface but are not granted explicitly:

Project role	How it is obtained
Administrator	Belongs to every user whose global role is Administrator or Super administrator. They always have full access to the projects of their company (super administrators — to all companies) and cannot be added or removed as members
Project manager	Belongs to the project owner. The level cannot be assigned to anyone from the Add project members dialog

Notes:

An access level may not exceed the user's global role. In the role selectors, levels above the user's global role are disabled and show the tooltip "Exceeds global user role" — for example, a user whose global role is Analyst cannot be granted developer access
Project ownership does not add permissions on its own. What a member may do is defined by their effective project role, not by who created the project
When a user works through an API key, their access to projects is the same as in the interface

Your access level in the projects list

The projects list has two columns that describe access:

Column	What is shown
Owner	The name of the project owner. If the owner no longer has access to project management, the name is shown in red with a tooltip explaining why ("User deleted" or "User without access to manage projects")
My access level	Your own project role — Administrator, Developer, Analyst, or Viewer. Your row is marked with an owner icon when you own the project. A dash means you have no explicit access level

Project visibility

Users only see the projects they may work with:

Global role	Projects visible in the list
Super administrator	All projects of all companies
Administrator	All projects of their company
Project manager	Projects they own and projects they were granted access to
Developer, Analyst, Viewer	Only projects they were granted access to

If you open a project you have no access to — through a direct link, or because your access was revoked while you were working — an error notification is shown and you are returned to the projects list.

Who may manage members

Managing members and ownership is available to:

the project owner
users with the global role Administrator or Super administrator

For everyone else, the Manage members action is not shown in the projects list, and an access-management request sent directly to the API is rejected. Every change of access and every ownership transfer is recorded in the system journal.

The Project members dialog

The dialog lists everyone who currently has access to the project in a single table:

Column	Description
First name, Last name	The member's name
Email address	The member's email
Global role	The user's role in the company
Project role	The access level inside this project. The owner's row is marked with an owner icon
Actions	Editing and removing the member

Each column supports sorting and filtering; the global role and project role columns are filtered by picking a value from a list. When nothing matches, the table shows "No members found".

The owner and the company administrators are listed because they always have access, so their rows carry no actions — only explicitly added members can be edited or removed.

Two buttons are available above the table: Add members and Change owner.

Adding members

The Add members button opens the Add project members dialog, where several members can be added at once:

Each row consists of a user selector and a project role selector. The user selector searches company users by name and email and lists only users who do not have access yet — company administrators are not offered, as they already have access
Selecting a user sets the highest access level their global role allows; the levels above it stay disabled
The Add more button adds another row and becomes unavailable once there is a row for every user who can still be added; the delete button next to a row removes it
Save grants access to every filled-in row at once, Cancel discards the whole form

Changing an access level

The edit action on a member's row opens the Edit project member dialog. The first name, last name, email address, and global role are shown read-only; only the project role can be changed. Save applies the new access level immediately.

Removing a member

The delete action on a member's row opens the Delete project member dialog, which asks for confirmation ("Are you sure you want to remove … from the project?"). On confirmation, the user loses access to the project: it disappears from their projects list, and if it was their active project they are returned to the projects list on their next request.

How access is resolved

When you open a project, your effective project role is resolved in this order:

Owner — if you own the project, your role in it follows your global role
Administrator — a user with the Super administrator role, or with the Administrator role in the project's company, always has administrator access, whether or not an explicit entry exists
Non-administrator added member — otherwise the access level from the project's member list is used
No access — if none of the above applies, the project is hidden from your list and cannot be opened

A project manager gets no access to a project of their company just by belonging to it. In a project they do not own, they work at the access level assigned to them in the member list: lowering it to Analyst or Viewer restricts what they can do, and removing them from the members takes the project away from them.

The project owner

Every project has exactly one owner. The user who creates a project becomes its owner. The owner may edit the project's properties, manage its members, transfer ownership, and delete the project.

Only users with the global role Project manager, Administrator, or Super administrator may own a project. Because an owner's standing can change over time, the interface shows the state of the owner record:

Owner state	Meaning	How it is shown
Valid	The owner is still a member of the company and holds a role that may own projects	Owner icon in the active color, tooltip "Project owner"
Deleted	The former owner was removed from the platform	The owner row is not shown in the member list; in the projects list the name is red with the tooltip "User deleted"
Downgraded	The owner is still in the company, but their global role no longer permits owning projects	Owner icon in the danger color, tooltip "Project owner without access to management"
Moved	The owner was moved to another company or is not activated	Owner icon in the danger color, tooltip "Project owner without access to management"

Transferring ownership

The Change owner button opens the Change project owner dialog:

Field	Description
Current owner	The current owner, read-only
New owner	A searchable list of users eligible to own the project — users of the project's company with the Project manager, Administrator, or Super administrator role. The current owner is not offered

Save transfers ownership. After the transfer:

the new owner gains full project management rights: editing the project, managing members, transferring ownership, and deleting the project
the previous owner loses those rights and keeps access according to their project access level. If their global role is Project manager, they are granted developer access to the project so they do not lose access to a project they used to own
an attempt to transfer ownership to a user who may not own projects is rejected

Access when a project is cloned

Cloning a project copies its member list, so the same users keep the same access levels in the clone. The user who performs the cloning becomes the owner of the new project; the owner of the source project, if they were not a member of it, is granted developer access to the clone.