Team 2.0 works and looks quite similar to today's regular team interface, but with one exception - it doesn't automatically assign tasks based on the team member's responsibility. Instead, tasks are distributed automatically based on the team member's assigned workflow stages - giving you more granular control of who can do what type of task.

On the input's way toward getting a delivery-ready annotation, it goes through a series of workflow stages. Each stage corresponds to one action in one of the workflow's different phases, such as the action “Correct” in the phase “Review”.

By assigning team members workflow stages, you define which stages they will automatically access tasks from and from which they won't.

You assign team members workflow stages either when adding the team member to the team or by editing the team member's workflow stages in the team member table.

You add team members in the same way as in other requests by clicking the "Add team members" button in the top right corner of the team member table. The difference is that instead of defining the team members' responsibility, you select which workflow stages they should be able to access tasks from.

You edit an existing team member's workflow stages by pressing the pen icon next to their workflow stages in the team member table. This opens a dialog from which you can change the team member's workflow stages.