Project-level roles reference

Reading time: 0 minute(s) (0 words)

Project role permissions apply to the projects users are assigned to. For example, a Project owner can manage users—add, delete, modify access—only within the projects they own.

This level roles entitle users to access project's underlying resources—services, data sources, and SLOs.

At the same time, project-level roles set limitations: users with the project-level roles can access resources attributed to their assigned projects.

This way, for composite SLOs, reports, and dashboards, users with the project-level roles will see (and can handle, if applicable) services and objectives attributed to their assigned projects only.

Project roles can be assigned either by Organization admins or by the Project owners.

Permission limitations

You can't assign a project role to Organization admins since this role has all the permissions in the organization by default.
Project owners can't invite new users to the organization or delete or suspend user accounts.

Project roles permission matrix

Select a feature from the drop-down menu to view its supported permissions:

Projects

Services

Service level objectives

Data sources

Alert policies

Alert methods

Alert silence

Metric health notifier

Reports & dashboards

SLI Analyzer & Replay

Labels

Data export

Event logs

Annotations (system & user)

Permission

Owner

Editor

Integrations user

Responder

Viewer

View project

Create project

Edit project

Delete project

note

All project roles can only view their own projects unless they have been granted Viewer permissions on other projects.

Project roles permission matrix​

Project roles permission matrix