Skip to content

Permissions reference

Project Management uses three levels above no access: Viewer, Editor, and Administrator.

Your level comes from the first of these that applies:

  1. A platform system administrator is an Administrator everywhere.
  2. Your role on the service, if you are an active member: viewer, editor, or admin.
  3. Membership of any team assigned to the service makes you an Editor.
  4. If the service has no teams assigned at all, you are a Viewer.
Action Level
View the project list and open a project Viewer
Create a project Editor
Edit a project and its settings Editor
Add, change, or remove team members Editor
Archive a project Administrator

Archiving is the end of the line — permanent deletion is deliberately not offered, so audit history survives.

Action Level
View the pool, allocations, utilisation, and capacity Viewer
Create and edit resources Editor
Create, change, end, or remove an allocation Editor
Sync a team from task assignees Editor
Deactivate a resource Administrator

A project’s Resources section shows + Add Member, Sync from Tasks, and the row edit and remove controls to everybody, including viewers. The buttons are visible; the actions are refused by the server.

If you are a viewer and an action fails with a permissions error, this is why — the control should not have been offered.

The project list and individual project pages are readable by any signed-in user with access to the service, without a project-management role check. Treat project descriptions, budgets, and risk registers as visible to the service’s users generally, and keep anything more sensitive out of them.

For what each role can actually do on screen, see the project views reference.