Organization and Project Roles

Overview

Your Organization is a unique structure that RedBrick AI creates for you and your team.

All of the work you do on RedBrick AI and any resources you use will be housed within your Organization. This includes your team members, your Taxonomies, your Projects, and more.

In RedBrick AI, a Project is a workspace to which you can upload data and inside of which you perform annotation work within a pipeline defined by you.

Within a Project, you can:

• upload images, volumes, and segmentation files;

• assign work to your labelers and reviewers on a Task level;

• perform and review annotation work;

• define Project-level permissions for labelers, reviewers, administrators, etc.;

• invite specific members of your team and regulate their access to various Stages;

• view a range of statistics on the quality of your labelers' work, time spent;

• configure custom toolkits and Project-level settings specific to your use case;

• and much, much more!

While all of your team members have to be invited to your Organization in order for them to access RedBrick AI, you can easily configure their permissions based on their Roles.

Roles

RedBrick AI offers role-based access control at two levels - the Organization level and the Project level. Each of these roles governs what actions a user can perform at the respective level.

Organization-level Roles

While each Organization can only have a single Org Owner, there is no limit to the number of Org Admins and Org Members an Organization can have.

Org Owner	Organization Level: Has access to all assets within an Organization; has the ability to create, edit, and delete assets, including the Organization itself. Project Level: Org Owners are automatically added to all Projects as Project Admins (see below).
Org Admin	Organization Level: Has access to all assets within an Organization; has the ability to create, edit, and delete assets, but not the Organization itself. Project Level: Org Admins are automatically added to all Projects as Project Admins (see below).
Org Member	Organization Level: cannot create or edit resources at the Organization level. Project Level: Org Members are not automatically added to any Projects, and must be invited to a Project by a Project Admin (see below).

Project-level Roles

Role	Permissions
Project Admin	Can perform administrative actions at the Project level, i.e. uploading data, assigning Tasks, editing Project Settings, and viewing Project Overview statistics & other user statistics.
Project Member	Can only annotate/review data (i.e. Tasks) that are assigned to them. Cannot view the activity of any other users.
Project Manager	Can manage Tasks and user permissions. Cannot access Project settings.

Common Role Configurations

• Labelers are often first added to an Organization as Org Members, added to relevant Projects as Project Members, and given access to the Label Stage by a Project Admin.

• Internal Reviewers are often first added to an Organization as Org Members and then added to relevant Projects as Project Admins, which gives them Project-wide Admin access.

• External Reviewers are often first added to an Organization as Org Members, added to relevant Projects as Project Members, and given access to any relevant Review Stages by a Project Admin.

• External Project Managers should be added to an Organization as Org Members and added to relevant Projects as Project Managers.

If you would like to change your Organization's Org Owner, please reach out to our support team at [e-mail].