Roles and permissions
Roles control who can view, assess, and administer your Pytheus workspace, so the right people own the right work.
Last updated September 22, 2026
Pytheus uses roles to control what each person can see and do. Matching roles to responsibilities keeps your assessment accurate and your workspace secure.
Why roles matter
A baseline is only as good as the people scoring it. You want domain owners assessing the capabilities they actually run, leaders reviewing the results, and a smaller group holding administrative control. Roles let you grant the right level of access without handing everyone the keys.
The organization roles
Workspaces assign access through five organization roles:
Owner. Full control of the workspace, including billing and ownership transfer.
Admin. Manage members, roles, domains, and organization settings.
Manager. Run the program day to day, including approving recommendations into the roadmap.
Contributor. Complete and update assessments and work within assigned domains.
Viewer. See scores, benchmarks, and roadmaps without changing the underlying data.
Choosing the right fit
Give people the least access they need to do their job. A leader reviewing the Pytheus Score may only need Viewer access, while a domain owner needs Contributor access to the capabilities they manage. Reserve Owner and Admin for the few who manage the workspace itself.
Because Pytheus scoring is deterministic and traceable, you can see how an assessment changed. Clear roles keep that history meaningful by ensuring the right person made each change.
Review your roles before you start adding people. When you are ready, see Inviting your team.