Every person has two kinds of role. A team role decides what they can do across the team: members, keys, billing, team algorithms. A project role decides what they can do inside one project. The two are set separately, and together they give each person exactly the access their work needs.
Team roles
Team Owners and Admins run the team, and they can work in every project without a project role. Researchers build team algorithms and models. Billing admins look after usage and billing. Viewers can look around but not change anything.
| What you can do | Owner | Admin | Researcher | Billing admin | Viewer |
|---|---|---|---|---|---|
| See team information | Yes | Yes | Yes | Yes | Yes |
| Create projects and work in every project | Yes | Yes | — | — | — |
| Invite members and change team roles | Yes | Yes | — | — | — |
| Manage team API keys and webhooks | Yes | Yes | — | — | — |
| Read the audit log | Yes | Yes | — | — | — |
| Create personal tokens | Yes | Yes | Yes | — | — |
| Write team algorithms and model images | Yes | Yes | Yes | — | — |
| Read team algorithms and model images | Yes | Yes | Yes | — | Yes |
| See usage and billing | Yes | Yes | — | Yes | — |
| Change billing and the storage limit | Yes | — | — | Yes | — |
| Change a project's recording privacy requirement | Yes | — | — | — | — |
Project roles
Inside a project, the Owner has full control. Editors do the everyday data work, everything except managing members or archiving and deleting the project. Uploaders add recordings and start processing. Reviewers check annotations and quality. Labelers label only the items assigned to them, and Collectors upload only to the collection tasks assigned to them. Viewers can read and download data but can't change anything.
| What you can do | Owner | Editor | Reviewer | Labeler | Viewer | Uploader | Collector |
|---|---|---|---|---|---|---|---|
| See the project and its data | Yes | Yes | Yes | — | Yes | Yes | — |
| Upload recordings | Yes | Yes | — | — | — | Yes | Assigned tasks |
| Start processing | Yes | Yes | — | — | — | Yes | — |
| Edit and publish the workflow | Yes | Yes | — | — | — | — | — |
| Label | Yes | Yes | Yes | Assigned items | — | — | — |
| Review annotations and quality | Yes | Yes | Yes | — | — | — | — |
| Create dataset versions and export | Yes | Yes | — | — | — | — | — |
| Train, evaluate and deploy models | Yes | Yes | — | — | — | — | — |
| Manage collection orders | Yes | Yes | — | — | — | — | — |
| Change name, description and secrets | Yes | Yes | — | — | — | — | — |
| Manage members, archive or delete the project | Yes | — | — | — | — | — | — |
A person can hold several project roles in the same project and gets everything each one allows. Labelers and Collectors work from My work, so they never browse the rest of the project.
How the two fit together
Team Owners and Admins can do everything in every project. Everyone else needs a project role to work in a project. A project with Team visibility can be opened read-only by anyone on the team; a Private project only by the people added to it.
Team Owners and Admins set team roles on the Members page of team settings. Project roles are set in the project under Settings, then Members, by the project Owner or a team Owner or Admin. See Team and members.
Who can open raw recordings
People appear in many recordings, so raw footage is protected until it has been anonymized. By default every project requires privacy processing. Until the anonymize step has finished for a recording, only three groups can open its raw files: the person who uploaded it, Owners, and project members who can both edit algorithms and manage the project's workflow. Everyone else, and every export, waits for anonymization.
If a project records no people or personal content, a team Owner can turn this off under the project's Recording privacy requirement, with a written reason that goes into the audit log. It applies to new uploads, and to existing recordings only if the Owner says so. No project needs written consent from the people recorded.