---
title: "Teams"
description: "Org-level and project-level team members: invite, roles, project access, add, and remove."
---

> Documentation Index
> Fetch the complete documentation index at: https://bergflow-docs.pages.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Teams

Team management exists at two levels:

- **Org.** Everyone in the organisation. **Teams** in the left sidebar.
- **Project.** Subset with access to that project. **Team** tab inside the project.

## Org-level team

**Teams** in the sidebar lists members: avatar + name, email, role, status, project access, actions.

Filter by **role** (Manager / Admin / Annotator / Reviewer) and **status** (Active / On leave / Terminated / Inactive). Search by name.

## Invite a member

**Invite team member** opens a sheet:

- **Name** (required)
- **Email** (required, validated)
- **Role:** Manager, Reviewer, or Annotator
- **Status:** Active (default), On leave, Terminated, or Inactive

**Send invite** dispatches the [invite email](/getting-started/access). Success and failure toasts explain the result.

**Edit member** on the ⋯ menu reopens the sheet (name / role / status). Email cannot change.

## Project access

**Project access, then Manage** on a member row lets managers grant or revoke projects.

You only see projects **you** can access. Deselecting revokes access. If the member has projects outside your scope, a yellow banner says you cannot manage those.

**Save changes** applies.

## Project-level team

Inside a project, **Team** shows members on *this* project only: name, email, role, and **Remove**. No status, project access, or kebab menu.

**Add team member:** multi-select org members not yet on the project, then **Add to project**.

**Remove** on a row drops them from the project only, not the organisation. Confirm in the dialog.

Source: https://bergflow-docs.pages.dev/account/teams/index.mdx