Understand project roles and permissions

Member

A Member has read-only project access. Members can:

• View the project overview and monitoring data.
• View project logs and log details.
• Search accessible projects and logs.
• Configure their own alert choices from My Alerts, when the project makes those channels available.
• Leave a shared project.

Members cannot create or edit logs, change project or monitor settings, manage members, or create project API tokens.

Developer

A Developer has Member access and can also:

• Create manual project logs.
• Create a project-scoped API token.
• Create logs through the API.
• Edit logs they created while they continue to have Developer or Admin access.
• Leave a shared project.

Developers cannot delete logs, manage project settings, change monitor or alert availability, or manage members.

Admin

An Admin can manage the complete project workspace. Admins can:

• Update and delete the project.
• Configure uptime and certificate monitoring.
• Choose which alert types and channels are available.
• Invite, remove, and change the roles of project members.
• Create, edit, move, and delete project logs.
• Create project-scoped API tokens.

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

Roles and 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, a token cannot create logs after its owner becomes a Member.

For token details, see Create and use API tokens.