Project roles: owner, editor, reviewer, viewer

Four project roles

A role is given for each project separately. The role you hold in one project says nothing about another.

• Owner: full control of scope and criteria, the team, export, archiving and deletion. A project always keeps at least one owner.
• Editor: searches, imports, uploads full text, starts processing and corrects extracted values. An editor cannot give final approval unless the owner also marks them "also reviewer".
• Reviewer: approves or rejects extracted values, records notes and verifies values.
• Viewer: reads everything and changes nothing.

Approval and export

Final approval of an extracted value can be given by reviewers, owners, and editors marked "also reviewer".

Owners can export. An owner can switch on "allow members to export" for the project, which lets editors and reviewers export as well.

Platform roles are separate

Platform roles are about the platform as a whole, never about a project. Platform staff do not see inside a private project unless they are members of it.

• Member: every new account. A member can create private projects and be invited to others.
• Platform admin: carries out the operational tasks they have been explicitly granted, such as seeing the account directory, suspending an account, retrying background tasks or seeing system status.
• Platform owner: appoints admins, manages integrations and institutions, can archive or delete any project after explicit confirmation, and reads the audit log.

What you can rely on

These rules are checked every time an action is carried out, not only when a page decides which buttons to show. If your role does not allow an action, the action is refused. To do something your role does not allow, ask a project owner to change your role.