Video Tutorial: Setting up Annotation team Using Project Roles

  • Updated

What we will cover

In this short tutorial, you will learn how to assign user to projects in Alegion Control and setup annotation teams. In addition to enabling workers to annotate specific projects, we will cover the reviewer role and how to enable workers to perform reviews for quality control and review scoring.



Video Transcript

At a high level, project roles in Alegion Control need little explanation. You can control who has access to projects and the actions they can perform on the annotation records in those projects. But let’s take a closer look so you can use the capability to its fullest.

It all begins when adding team members. When you add new team members you can add them as administrator. An administrator can add and edit projects, and this includes setting project roles for other team members.

Administrators can grant or revoke permissions at any time, or disable accounts. Administrators can also open records for annotation or review and archive projects and records. You can have as many administrators as you like.

To set roles per-project, create team members who are not administrators and set their roles for each project they should have access to.

In this example, I’ll open the Workers tab of my Supply Logistics project and assign one user as an annotator and one as a reviewer. Once assigned, these users will only have access records in projects they have been assigned to.

Reviewers can annotate new records, but can also open records in the review state to make corrections or approve annotations for final results.

Annotators can annotate new records, but don't have access to open records for review.

As you would expect, a single user can have different roles on multiple projects.

Project roles enable a simple and effective access control to your Alegion projects.



Share This