> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/getting-started/creating-and-customizing-board-views.md).

# Creating and Customizing Board Views

{% columns %}
{% column %}
**What is covered**

* Create a Board View
* Choose lane (group-by) settings
* Apply filters and sorting
* Save and share a Save View
  {% endcolumn %}

{% column %}
**At a glance**

* **Time:** \~5–10 minutes
* **Access:** Project access with view permissions
* **Prerequisites:** a Project with items and at least one status field
  {% endcolumn %}
  {% endcolumns %}

### Overview

Board Views organize work into lanes. They work best for workflow and status-driven reviews.

{% hint style="info" %}
Screenshot placeholder: Board View with 3+ lanes and several cards.
{% endhint %}

### Key Concepts

* **Lane field**: field used to group cards into lanes
* **Card order**: ordering inside a lane (sorting)
* **Save View**: stored configuration for repeatable boards

### How It’s Used

Use Board Views for standups and workflow reviews. Use lane fields such as Status or Assignee for ownership clarity.

### Benefits

* Faster workflow review through visual lanes
* Clear ownership through grouped lanes

### Setup Steps

#### 1) Create a new Board View

Open the view selector. Choose **New view**. Select **Board**.

{% hint style="info" %}
Screenshot placeholder: new view dialog with Board selected.
{% endhint %}

{% hint style="info" %}
GIF placeholder: create a Board View from the view selector.
{% endhint %}

#### 2) Configure lanes

Pick a lane field. Common lane fields are **Status**, **Assignee**, or **Priority**.

{% hint style="info" %}
Screenshot placeholder: lane (group-by) settings panel.
{% endhint %}

#### 3) Drag items between lanes

Drag a card to another lane. This updates the lane field.

{% hint style="info" %}
GIF placeholder: drag a card to a different lane and show the field update.
{% endhint %}

#### 4) Filter and sort

Use filters to focus the board. Use sorting to control card order.

{% hint style="info" %}
Screenshot placeholder: filters applied to a Board View.
{% endhint %}

#### 5) Save and share

Most changes save automatically. Set visibility to **Private** or **Team**, if available.

{% hint style="info" %}
Screenshot placeholder: view visibility options in the share modal.
{% endhint %}

### Best Practices

* Keep shared boards stable and predictable.
* Standardize lane fields for comparable reporting.
* Use filters to create focused review boards.

### Summary

Board Views group work into lanes for workflow reviews. Save Views store the configuration for repeatable use.

Related:

* [Filtering and Sorting Data](/getting-started/filtering-and-sorting-data.md)
* [Save Views and Templates](/getting-started/save-views-and-templates.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.transform.ai/getting-started/creating-and-customizing-board-views.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.