---
title: Boards
description: Create a board, rename and reorder it, set up its status columns, and delete it when it is finished with.
section: Boards and tickets
order: 1
---

# Boards

A board is one kanban wall: a set of status columns with tickets in them. Every
board belongs to a workspace, and a workspace can hold as many boards as its
plan allows.

## Before you start

- You need a workspace role that can write — **owner**, **admin** or **member**.
  A **viewer** can open boards and read everything on them, but every button
  described here will return "Your role in this workspace is read-only". See
  [Roles and permissions](/docs/workspaces-and-access/roles-and-permissions).
- On the **free** plan a workspace may have **2 boards**. Trying to create a
  third is refused with a message naming the limit and the price to lift it.
  The **Pro** plan has no board limit. Boards you have deleted do not count.
- Whoever creates a board is given access to it. Owners and admins see every
  board in the workspace; members only see boards they have been added to. See
  [Board access](/docs/workspaces-and-access/board-access).

## Create a board

1. In the left sidebar, under **Boards**, click **New board**.
2. Type a name (up to 200 characters).
3. Click **Create board**.

Laver opens the new board straight away. Pressing `Escape` in the name field
cancels without creating anything.

If the workspace has no boards at all, the main panel shows **No boards yet**
with a **Create a board** button that does the same thing.

## What a new board starts with

Every new board is created with three status columns:

| Column      | Notes                                                     |
| ----------- | --------------------------------------------------------- |
| Backlog     | First column, where a ticket lands if you do not pick one |
| In progress |                                                           |
| Done        | Marked as the board's **completion column**               |

It starts with no tickets, and with you as its only member.

The completion column matters in two places: it is the column the card hover
shortcut moves a ticket to by default, and it is what a sprint rollover treats
as "finished". See [Sprints](/docs/boards-and-tickets/sprints).

## Rename a board

1. Open the board.
2. Click the pencil (**Rename board**) next to the board name in the header.
3. Edit the name and press `Enter`, or click the tick.

`Escape` or the cross cancels. Names can be up to 200 characters, and ordinary
boards are allowed to share a name. The one exception is sprints: a sprint
board is named from its series, and creating one is refused if a board of that
name already exists.

## Reorder boards in the sidebar

Board order is a property of the board, so the order you set is the order
everyone in the workspace sees.

- **With a mouse:** drag the grip handle at the left of a board row up or down
  and drop it. A line shows where it will land.
- **With a keyboard:** focus the grip handle (its label is
  "Reorder _board name_") and press `Arrow Up` or `Arrow Down`. Each press
  moves the board one place and saves immediately.

If someone else adds or removes a board while you are dragging, the save is
refused with "The board list changed. Refresh and try again."

## Delete a board

1. Open the board.
2. Click the bin icon (**Delete board**) in the board header. On a narrow
   screen it is in the account menu instead.
3. Confirm the browser prompt.

Deleting removes the board and its tickets from the workspace for everybody,
and **there is no way to restore it from the app**. Laver takes you to the next
board in the sidebar.

There is no separate "archive" action for boards in the product: **Delete** is
the only option, and it is what frees a slot on the free plan's board limit.

If the board you delete is the live board of a sprint series, that series is
switched off and stops rolling over. Earlier sprint boards are untouched.

## Configure status columns

Columns are the vertical lanes on the board. Changing them affects everyone
looking at the board.

### Add a column

1. Scroll to the right-hand end of the board to the **Add column** panel.
2. Click **Add column**, type a name (up to 100 characters), and submit.

The new column is appended after the existing ones. `Escape` cancels.

### Rename a column

1. Hover the column header and click the pencil (**Rename column**).
2. Edit the name and press `Enter`, or click the tick.

Renaming is safe: tickets stay where they are, and a renamed completion column
stays the completion column.

### Reorder columns

- **With a mouse:** drag the grip handle in the column header left or right.
- **With a keyboard:** focus the grip handle and press `Arrow Left` or
  `Arrow Right`.

As with boards, a partial or stale list is refused with "The column list
changed. Refresh and try again."

### The completion column

Exactly one column per board is marked as the completion column. Laver sets
this when the board is created — it is the last of the three default columns,
**Done** — and:

- **It cannot be changed afterwards.** There is no control in the app and no
  API field for moving the completion mark to a different column.
- **Columns cannot be deleted.** There is no delete action for a status column
  in the app or in the API.

So if you want a different name on the completion column, rename **Done**
rather than adding a new column beside it. Columns you no longer need can be
moved to the far right, but they will stay on the board.

## Show two boards side by side

With more than one board in the workspace, **Split view** in the board header
opens a second board in a pane beside the current one, chosen from a dropdown.
The two panes are independent: you can read and edit in both, but you cannot
drag a card from one pane into the other. Close it with the cross on the pane
bar or by pressing **Split view** again.

## If something is refused

Board writes can fail for reasons that have nothing to do with the board — an
unpaid invoice makes a workspace read-only, and a workspace with no
subscription is closed to everyone until one is started. The message says
which. See [Errors](/docs/troubleshooting/errors).
