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

# Manage review work

> Assign rows to reviewers, filter and organize the review queue, and customize table views to distribute and track human review across your team.

As review scales across a team, you need to distribute work, focus reviewers on the right rows, and track progress. This page covers assigning rows, filtering the review queue, and customizing how the review table looks.

## Assign rows for review

You can assign rows in logs, experiments, and datasets to team members for review, analysis, or follow-up action. Assignments are particularly useful for human review workflows, where you can assign specific rows that need human evaluation and distribute review work across multiple team members.

To assign a row to a team member from any table view (logs, experiments, or datasets):

1. Select the row.
2. Select **<Icon icon="flag" /> Assign**.
3. Choose a member to assign.

<Tip>
  Team members receive email notifications when rows are assigned to them.
</Tip>

## Filter review data

The [**<Icon icon="list-checks" /> Review**](https://www.braintrust.dev/app/~/review) page shows any spans that have been flagged for review within a given time range. Each project provides default table views with common filters, including:

* **Default view**: shows all records.
* **Awaiting review**: shows only records flagged for review but not yet started.
* **Assigned to me**: shows only records assigned to you for review.
* **Completed**: shows only records that have finished review.

Use the <Icon icon="layers-2" /> **View** menu to switch between views.

You can also use the [**<Icon icon="list-filter" /> Filter**](/observe/filter) menu to focus on specific subsets for review. Use the **Basic** tab for point-and-click filtering, or switch to **SQL** to write precise queries. For example, filter by scores (e.g., `scores.Preference > 0.75`) to find highly-rated examples, or use [tags](/annotate/labels#apply-tags) to mark items for "Triage" and review them all at once.

<Tip>
  Built-in views (such as "All logs view") cannot be modified, but you can create [custom table views](#create-custom-table-views) based on custom filters and display settings.
</Tip>

## Customize the review table

### Show and hide columns

Select <Icon icon="settings-2" /> **Display** > <Icon icon="columns-2" /> **Columns** and then:

* Show or hide columns to focus on relevant data.
* Reorder columns by dragging them.
* Pin important columns to the left.

All column settings are automatically saved when you save a view.

<Note>
  Free-form human review scores and scores that write to expected output appear automatically as columns in the dataset, review, logs, and experiment tables, marked with the <Icon icon="list-checks" /> review icon. You don't need to add them as custom columns.
</Note>

### Use kanban layout

The kanban layout organizes flagged spans into three columns based on their review status:

* **Backlog**: spans flagged for review but not yet started.
* **Pending**: spans currently being reviewed.
* **Complete**: spans that have finished review.

To use the kanban layout:

1. On the [**<Icon icon="list-checks" /> Review**](https://www.braintrust.dev/app/~/review) page, select <Icon icon="settings-2" /> **Display** > **Layout** > **Kanban**.
2. Drag cards between columns to update review status. Changes save automatically.
3. Click any card to open the full trace for detailed review.

Each card displays the span name, creation date, assignees, and a preview of the input and output.

### Create custom table views

To create or update a custom table view:

1. Apply the filters and display settings you want.
2. Open the <Icon icon="layers-2" /> menu and select **Save view\...** or **Save view as...**.

<Note>
  Custom table views are visible to all project members. Creating or editing a table view requires the **Update** project permission.
</Note>

### Set default table views

You can set default views at three levels:

* **Organization default**: Visible to all members when they open the page. This applies per page. For example, you can set separate organization defaults for Logs, Experiments, and Review. To set an organization default, you need the **Manage settings** organization permission (included by default in the **Owner** role). See [Access control](/admin/access-control) for details.
* **Project default**: Overrides the organization default for everyone viewing this project. To set a project default, you need the project-level **Update** permission. Project admins can set project defaults even without organization-level permissions. See [Access control](/admin/access-control) for details.
* **Personal default**: Overrides the project and organization defaults for you only. Personal defaults are stored in your browser, so they do not carry over across devices or browsers.

To set a default view:

1. Switch to the view you want by selecting it from the <Icon icon="layers-2" /> menu.
2. Open the menu again and hover over the currently selected view to reveal its submenu.
3. Choose <Icon icon="flag-triangle-right" /> **Set as personal default view**, <Icon icon="bookmark" /> **Set as project default view**, or <Icon icon="pin" /> **Set as organization default view**.

To clear a default view:

1. Open the <Icon icon="layers-2" /> menu and hover over the currently selected view to reveal its submenu.
2. Choose <Icon icon="flag-triangle-right" /> **Clear personal default view**, <Icon icon="bookmark" /> **Clear project default view**, or <Icon icon="pin" /> **Clear organization default view**.

Default view settings are mutually exclusive on a given view. Setting one type of default on a view automatically clears any other default that was previously set on the same view.

When a user opens a page, Braintrust loads the first match in this order: personal default, project default, organization default, then the standard "All ..." view (for example, "All logs view").

## Next steps

* [Score traces and datasets](/annotate/human-review/score-traces) in review mode
* [Review with multiple reviewers](/annotate/human-review/multiple-reviewers) on the same span
* [Build datasets](/annotate/datasets/create#promote-traces-from-logs) from reviewed logs
