> AI agents: this is one page from Mammoth Analytics documentation. The index of all pages as Markdown is https://docs.mammoth.io/llms.txt. Append `.md` to any docs URL, or send `Accept: text/markdown`, to get Markdown.

# Project roles & permissions

> Compare what Project Admins and Project Editors can do in a Mammoth project, how roles are assigned, and how workspace roles relate to project roles.

This page is for anyone deciding which role to give a teammate, and for Project Admins managing access. Mammoth uses two project roles to control what team members can do inside a project: **Project Admin** and **Project Editor**. Roles are set per project, so a user can be an Admin in one project and an Editor in another.

## Role overview

| Role | Description |
| --- | --- |
| **Project Admin** | Full control over the project: configure settings, manage team members, delete the project, plus all Editor capabilities |
| **Project Editor** | Work with data and pipelines: access, create, edit, and manage datasets and automations within the project |

## Permission matrix

Project Admins can do everything Project Editors can, plus edit project settings, delete the project, manage project members, and create, update, or delete Live Connections. Editors can view and change datasets, views, pipelines, and Live Connection queries, but cannot manage members or Live Connections themselves.

The full workspace, project, and dashboard matrix is on the [Access Control](https://docs.mammoth.io/learn/security-overview/access-control/#roles-and-permissions-matrix) page.

## Assigning roles

Roles are assigned:

- **During project creation**: When you set access to "Some people in this workspace", you assign each user a role in the creation modal.
- **In the Share Project modal**: Open the Share button or Manage Users from the project menu, then use the role dropdown next to each user's name.
- **When adding new members**: The role defaults to Editor; change it immediately after adding.

There is no limit on the number of Project Admins a project can have.

## The creator's role

The user who creates a project is automatically assigned **Project Admin**. This cannot be changed at creation time.

## Workspace roles and project roles

Workspace roles (Owner, Member) and project roles (Admin, Editor) are separate systems. A user's workspace role does not automatically determine their project role, but Workspace Owners have broad project-level overrides:

| Workspace role | Project override |
| --- | --- |
| **Workspace Owner** | Can add users to any project, delete any project, and view all project names—regardless of project membership or role |
| **Workspace Member** | No project-level overrides. Access is determined solely by project role assignment |

This means:

- A **Workspace Owner** can delete any project or add users to it even if they are not a project member.
- A **Workspace Member** with no project role cannot see a project set to "Some people" or "Only me".

## Changing a user's role

Any **Project Admin** can change another user's role.

**Prerequisite**: You are a Project Admin on the project.

1. Open the Share Project modal (Share button in the header, or project menu → Manage Users).
2. Find the user in the "Shared with" list.
3. Click the role dropdown next to their name.
4. Select **Project Admin** or **Project Editor**.

**Expected result**: The change takes effect immediately.

To remove a user entirely, select **Remove** from the role dropdown.

## Frequently asked questions

**Q: Can a Project Editor change project settings?**\
A: No. Editing project settings (name, color, date handling, access level) requires the Project Admin role.

**Q: Can a Project Editor add new users?**\
A: No. Only Project Admins (and Workspace Owners) can add users to a project.

**Q: Can there be multiple Project Admins?**\
A: Yes. There is no limit on the number of admins per project. Granting Admin to multiple users is recommended to avoid a single point of failure if the primary admin leaves.

**Q: What happens if the only Project Admin leaves the project?**\
A: The project still exists but will have no Project Admin. A Workspace Owner can still add users to the project and delete it using workspace-level overrides. Assign a replacement admin before leaving.

**Q: Is there a read-only "viewer" role?**\
A: No. The two roles available to users are **Project Admin** and **Project Editor**.

**Q: I want to give someone access to view data but not edit it. What role should I use?**\
A: Use **Project Editor**. It is the standard working role for all data access. A read-only viewer role is not currently available in the UI.

## Related articles

- [Sharing a project](https://docs.mammoth.io/learn/projects/project-sharing/): Add users and assign roles
- [Project settings](https://docs.mammoth.io/learn/projects/project-settings/): Configure access level and project details
- [Creating a project](https://docs.mammoth.io/learn/projects/create-project/): Set roles when first creating a project
- [Projects overview](https://docs.mammoth.io/learn/projects/): Understanding projects in Mammoth

---

**Need help?** Check the [troubleshooting guide](https://docs.mammoth.io/learn/troubleshooting/) or contact Mammoth Support.

---
Source: https://docs.mammoth.io/learn/projects/project-roles-and-permissions.md · Updated: 2026-10-13