Understand project roles and permissions

Project roles control what accepted members can view or change. Use the lowest role that gives a teammate the access they need.

Member

Members can view the project overview, monitoring data, Activity, log and maintenance details, and generated reports. They can configure personal delivery choices under Settings > Alerts and leave a shared project.

Members cannot create logs, environments, maintenance, reports, or API tokens. They also cannot change project settings, manage members, share or delete reports, or delete environments.

Developer

Developers have Member access and can also:

• Create manual logs and edit logs attributed to their account.
• Create non-primary environments.
• Schedule, update, end, or cancel maintenance.
• Generate immutable project reports.
• Create project-scoped API tokens that can create environments and logs and manage maintenance.

Developers cannot change General, Monitoring, or Project Alerts settings; manage members; delete logs or environments; share reports publicly; or delete reports.

Admin

Admins can manage the complete project workspace. They can update or delete the project, configure monitoring and alert availability, manage members, create and delete environments, manage all logs and maintenance, generate reports, create or disable report share links, delete reports, and create API tokens.

A project must always have at least one Admin. The account that created the project is added as an Admin, and that owner's role cannot be changed.

API access

API tokens remain tied to both their owner and one project. A token stops being sufficient if its owner loses the required project role or project access. For example, after an owner becomes a Member, the token cannot create environments or logs or change maintenance.