INTRODUCTION

Roles & permissions

4min

The new roles and permission system is being rolled out over the next few weeks. During this transition period, the information below may not be accurate with what you see in the platform.

Organisation roles

In an organisation, a user can have one or several of the following roles:

Member, Stopwatch reporter, Stopwatch manager, Team manager and Admin.

The table below describes the high-level access (in terms of features and actions) granted to each role.

Organisation roles control organisation-level features and actions. Whether someone can access workspace-level features and actions depends on their workspace role.

ο»Ώ

Member

Stopwatch reporter

Stopwatch manager

Team manager

Admin

My tasks

βœ…

βœ…

βœ…

βœ…

βœ…

Campus

βœ…

βœ…

βœ…

βœ…

βœ…

My performance

βœ…

βœ…

βœ…

βœ…

βœ…

My examinations

βœ…

βœ…

βœ…

βœ…

βœ…

Exams

βœ…

βœ…

βœ…

βœ…

βœ…

Team management

❌

❌

βœ…

βœ…

βœ…

Team overview

❌

❌

❌

βœ…

βœ…

Team member details

❌

❌

❌

βœ…

βœ…

Manage team report

❌

❌

βœ…

❌

βœ…

Idle members

❌

❌

❌

βœ…

βœ…

Platform administration

❌

❌

❌

❌

βœ…

User management

❌

❌

❌

❌

βœ…

Report time

❌

βœ…

❌

❌

❌

If you are looking to invite users to your organisation, and/or assign them organisation roles, you can learn more about how to do that under the section platform administration.

Workspace roles

In a workspace, a user that is part of the organisation that owns the workspace can have one or several of the following roles:

Member, Annotation manager, Project manager, Developer and Admin.

If a user is part of an organisation that has been invited as a collaborator to the workspace, the roles available to them will depend on the collaboration type assigned to their organisation. How workspace roles relate to collaborator types are described in this table.

The table below describes the high-level access (in terms of features and actions) granted to each role.

Workspace roles control workspace-level features and actions. Whether someone can access request-level features and actions will depend on their organisation's assigned request role in the specific request.

ο»Ώ

Member

Annotation manager

Project manager

Developer

Admin

Receive tasks

βœ…

βœ…

βœ…

βœ…

βœ…

Project management

❌

βœ…

βœ…

βœ…

βœ…

Create projects

❌

❌

βœ…

❌

βœ…

Create request

❌

❌

βœ…

❌

βœ…

Request

❌

βœ…

βœ…

βœ…

βœ…

Annotation instructions

❌

❌

βœ…

βœ…

βœ…

Insights

❌

❌

❌

βœ…

βœ…

Workspace management

❌

βœ…

βœ…

βœ…

βœ…

Workspace settings

❌

❌

❌

❌

βœ…

Members

❌

βœ…

βœ…

βœ…

βœ…

Collaborators

❌

❌

βœ…

βœ…

βœ…

API credentials

❌

❌

❌

βœ…

βœ…

If you are looking to invite members to a workspace, and/or assign workspace roles, you can learn more about how to do that under the section workspaces.