# Project Roles and Permissions in TestOwl

:::lead
Every project has a team, and every member is assigned a role that determines what they can see and do within the project.
:::

Roles are **per project**. The same person can be an Owner in one project and a Viewer in another. Each role includes everything the role below it can do.

## Role permissions

| What you can do | Owner | Admin | Editor | Viewer |
| --- | :---: | :---: | :---: | :---: |
| View the project, Dashboard, tests, suites, flows, environments, run history, and reports | ✅ | ✅ | ✅ | ✅ |
| Record and create Test Suites, Test Cases, and Flows; edit their steps | ✅ | ✅ | ✅ | ❌ |
| Run tests and use the Import Wizard | ✅ | ✅ | ✅ | ❌ |
| Create and edit Environments | ✅ | ✅ | ✅ | ❌ |
| Create and edit Variables, Secrets, Tags, and Masking Rules | ✅ | ✅ | ✅ | ❌ |
| Restore items from the Recycle Bin | ✅ | ✅ | ✅ | ❌ |
| **Delete** Test Suites, Test Cases, Flows, Environments, Variables, Secrets, Tags, Masking Rules, and runs | ✅ | ✅ | ❌ | ❌ |
| Permanently delete items from the Recycle Bin | ✅ | ✅ | ❌ | ❌ |
| Create, edit, pause, and delete [Schedules](/docs/running-and-results/schedules) | ✅ | ✅ | ❌ | ❌ |
| Invite, change, and remove team members | ✅ | ✅ | ❌ | ❌ |
| Rename the project and manage its settings | ✅ | ✅ | ❌ | ❌ |
| Manage plan and [Billing](/docs/team-and-account/billing) | ✅ | ❌ | ❌ | ❌ |
| Delete the project | ✅ | ❌ | ❌ | ❌ |

## Owner

The **Owner** has full control over the project, including the things no one else can do: managing billing and plans, and deleting the project. Owners can also do everything an Admin can.

A project can have more than one Owner — an existing Owner can invite someone as an Owner or promote another member to Owner.

## Admin

Admins run the project day to day. They can do everything an Editor can, and also:

- Delete tests, suites, flows, environments, variables, secrets, tags, masking rules, and runs.
- Create and manage schedules.
- Invite people and manage team members.
- Rename the project and change project settings.

Admins can't manage billing or delete the project, and they can't grant or change the **Owner** role.

## Editor

Editors build and maintain tests. They can:

- Record tests and create and edit Test Suites, Test Cases, and Flows.
- Run tests, against any environment.
- Import existing tests.
- Create and edit Environments, Variables, Secrets, Tags, and Masking Rules.
- Restore deleted items from the Recycle Bin.

Editors can't delete anything, manage schedules, or manage the team.

## Viewer

Viewers have read-only access. They can browse the Dashboard, Test Suites, Test Cases, Flows, Environments, Run History, and Reports, and download report PDFs where the plan allows. On the User Management page a Viewer only sees their own membership — other members are hidden.

Viewers can't change anything or start runs.

![Project Members](/images/team-and-account/project-roles/project-members.png)

## Managing roles

Owners and Admins manage the team from **Settings → User Management**. The rules are:

- You can only assign, change, or remove roles **up to your own level**. An Admin can manage Admins, Editors, and Viewers but not Owners; only an Owner can add, change, or remove an Owner.
- You **can't change your own role** or remove yourself from a project. Ask another Owner or Admin to do it.
- Role changes take effect immediately — the person doesn't need to sign out and back in.
- Removing a member revokes their access straight away. It doesn't delete the tests, flows, or other items they created.

See [Inviting Team Members](/docs/team-and-account/inviting-members) for how to add people.

## Team size

The number of seats depends on your plan — 3 on Trial and Starter, 5 on Pro, and 15 on Scale. Every active member, including the Owner, uses a seat, and so does each invitation that hasn't been accepted or expired yet. See [Plans & Usage](/docs/team-and-account/plans-and-usage).

## Next steps

::::cardgrid
:::card{title="Inviting Team Members" href="/docs/team-and-account/inviting-members"}
Invite teammates to collaborate on your project.
:::

:::card{title="Plans & Usage" href="/docs/team-and-account/plans-and-usage"}
Learn about project limits and available resources.
:::
::::