Pipelines Docs is in beta — content is actively being added.
Platform GuideOrganizations & Projects

Team Management

Invite users, assign roles, and manage contributors across your organization and projects.

Team management in Pipelines operates at two levels: organization-wide and per-project. Organization-level management handles who belongs to your org and their top-level roles, while project-level management controls who can access each project and what they do within it.

Organization-level team management

Organization-level team management lives under People in the admin sidebar. The People page has two tabs:

  • Admins — manage Org Admins and Project Admins
  • Contributors — manage contributors across projects

Inviting admins

  1. Navigate to PeopleAdmins tab.
  2. Click Invite Admin to Platform.
  3. In the dialog, choose the admin type: Org Admin or Project Admin.
  4. Enter the user's Name and Email address.
  5. For Project Admins, optionally select an initial project assignment.
  6. Click Invite Org Admin or Invite Project Admin (the button label matches your selection).

The user receives a magic link email. Clicking the link activates their account and signs them in. Until activated, the user appears with a Pending status on the Admins tab.

Assigning admins to projects

In addition to inviting new admins, you can assign existing Project Admins to additional projects:

  1. Navigate to PeopleAdmins tab.
  2. Click Assign Admins to Projects.
  3. Select the admin(s) and the target project(s).
  4. Choose an access level: Owner (full read/write) or Viewer (read-only).

Managing admins

The Admins tab has two sub-tabs:

  • Organization Admins — users with org-wide access to all projects and settings. Shows Name, Email, Status, and Last Seen.
  • Project Admins — users with admin access to specific projects. Shows Name, Email, Owner projects, Viewer projects, Status, and Last Seen.

From the Admins tab you can:

  • Invite new admins to the platform
  • Assign existing Project Admins to additional projects (with Owner or Viewer access)
  • Remove admin access (the user retains any other project-level roles they hold)

Org Admins cannot remove themselves. This prevents accidental lockout.

Adding contributors to projects

  1. Navigate to PeopleContributors tab.
  2. Click Add Contributor.
  3. Choose the add method:
    • Select from Organization — pick existing org members and assign them to one or more projects. These users are added immediately and do not receive any notification — they will discover the new project the next time they view their project list.
    • Invite New Contributor — enter an email address and optional name, then select the target projects. A magic link invitation email is sent.
  4. Click Add or Invite.

Bulk inviting users

You can add multiple users at once via CSV upload:

  1. Navigate to PeopleContributors tab.
  2. Click Bulk Invite Users.
  3. Upload a CSV file with the following columns:
ColumnRequiredDescription
emailYesThe user's email address.
project_nameYesMust match an existing project name exactly.
nameNoThe user's display name.
roleNoA contributor type name defined in the target project (e.g., "Expert").
  1. The dialog shows available projects and contributor roles for reference.
  2. Click Invite Users to process the file.

New users receive magic link invitation emails. Existing org members are assigned to the specified projects silently (no notification sent).

CSV uploads support up to 5,000 rows per file and are rate-limited to 10 uploads per 5 minutes per user.

Removing users from the organization

On the Contributors tab, click the remove icon next to a user to remove them from the organization entirely. This revokes access to all projects and the user would need to be re-invited to rejoin.

Removing a user from the organization does not automatically release their in-progress tasks. Claimed tasks remain assigned and must be manually released by an admin, or will be released automatically if a claim timeout is configured on the pipeline. See Claiming Work.

Project-level team management

Project-level team management lives on the Team page within each project (under the Manage section in the sidebar). The Team page has two tabs:

  • Contributors — team members who complete tasks
  • Admins — project-level administrators

Only Org Admins and Project Admin Owners can manage the team.

Adding users to a project

  1. Navigate to your project's Team page.
  2. Click Add User.
  3. Choose a role: Contributor or Project Admin.
  4. For Contributors:
    • Select existing org members (added immediately, no notification sent), or invite a new user by email (a magic link invitation is sent).
    • Optionally assign one or more contributor types.
  5. For Project Admins:
    • Select existing admins from the organization.
    • Choose an access level: Owner (full read/write) or Viewer (read-only).
  6. Click the action button (e.g., Add Contributor, Add Project Admin).

Bulk inviting contributors

The project Team page also supports CSV-based bulk invites:

  1. Click Bulk Invite Contributors on the Team page.
  2. Upload a CSV file with the following columns:
ColumnRequiredDescription
emailYesThe user's email address.
nameNoThe user's display name.
roleNoA contributor type name defined in the project.
  1. The dialog shows available contributor roles for reference.
  2. Click Invite Users to process the file.

New users receive magic link invitations. Existing org members are assigned to the project silently.

Contributor types

Contributor types are custom labels that categorize contributors within a project (e.g., "Expert", "Reviewer", "QA"). Every project must have at least one contributor type, and one must be marked as the default.

When a new project is created, two contributor types are set up automatically: Expert (default) and Reviewer. You can rename, add, or remove these as needed.

Managing contributor types

  1. Go to the project's Team page.
  2. Click Manage Contributor Types.
  3. The dialog shows a table of existing types with their name, description, and default status.
  4. Click Add Type to create a new type with a name and optional description.
  5. Use the row actions to:
    • Set as Default — mark a type as the default (assigned to new contributors who aren't given a specific type).
    • Edit (pencil icon) — rename or update the description.
    • Delete (trash icon) — remove the type.

You cannot delete the default contributor type or the last remaining type. To delete the current default, first set another type as the default.

Deleting a contributor type removes the type assignment from any contributors who had it. A confirmation dialog warns: "Contributors assigned this role will have their role set to null." Affected contributors appear as "No types assigned" on the Team page until you reassign them. Any instruction visibility or pipeline node restrictions tied to the deleted type are also removed.

How contributor types are used

  • Node claim restrictions — pipeline nodes can require a specific contributor type, preventing other contributors from claiming those tasks.
  • Per-type claim limits — pipelines can set maximum concurrent claim limits per contributor type.
  • Work schedule restrictions — contributor types can have per-type work schedules that control when contributors of that type can claim tasks.
  • Instruction visibilityInstructions can be scoped to specific contributor roles, so only contributors with a matching type see the instruction.
  • Task filtering — filter and assign tasks based on contributor type.
  • Bulk operations — select multiple contributors on the Team page and use Change Type to reassign types in bulk.

Removing team members

Remove a user from a project by clicking the remove icon next to their name on the Team page. You can also select multiple users and click Remove Selected for bulk removal.

Removing a user from a project:

  • Revokes their access to the project immediately.
  • Does not remove them from the organization — they retain access to other assigned projects.
  • Does not automatically release their in-progress tasks — claimed tasks remain assigned and must be manually released or will be released by the claim timeout if one is configured on the pipeline.

Project Admins cannot remove themselves from their own project.