Overview

Quickstart

Before you start#

You need a Laver account. A new workspace starts on the free plan — no card, no deadline, nothing to switch on first.

Step Role required
Create a workspace any signed-in user (you become its owner)
Create a board owner, admin, or member
Create, assign, and move tickets owner, admin, or member, on a board you can reach
Add a wiki page owner, admin, or member
Invite a colleague owner or admin
Upgrade the workspace to Pro owner only

See the full table in Roles and permissions.

1. Sign in and pick a workspace#

Sign in. You land on the dashboard, which is the board view. Click the Workspace switcher at the top of the sidebar to list your workspaces or create a new one.

2. Open the starter board, or create one#

Every new workspace comes with a board called General. To create another, click the three dots beside Boards, choose New board, type a name, and click Create board.

3. Read the three starting columns#

Every new board starts with the same three columns: Backlog, In progress, Done. Done is the board's completion column — see Statuses and workflow.

4. Create a ticket#

Click Add task at the bottom of Backlog, or press C. Type a title and click Add task.

5. Assign it#

Click the card to open the ticket, then click Manage assignees and pick yourself or any active workspace member.

6. Move it through the workflow#

Drag the card, change the Status dropdown, or use the hover tick shortcut. Move your ticket to In progress, then to Done.

7. Add a wiki page#

Under Workspace tools, click Wiki, click the + beside Pages, name the page and start typing — it saves as you write. See Wiki pages.

8. Invite a colleague (owner or admin)#

Open User access → People → Invite user, enter their email, choose a role, tick board access for viewers/members, and Send invitation. They get an emailed link that expires in seven days.

What you get without paying, and what upgrading is for#

On free On Pro
1 workspace you own Unlimited
3 boards Unlimited
3 billable seats Unlimited
100 MB of storage 10 GB per billable seat, pooled
2 automation rules per board Unlimited

Four things are held back for Pro: guests, publishing a wiki page, publishing a board as a read-only roadmap, and private wiki pages. Everything else — boards, tickets, the wiki, sprints, imports, automations, the API and the MCP server — is on both plans.

Where next#

  • Sprints — turn a board into a repeating series.
  • Agent quickstart — issue an API key and drive a board from a script.
  • Errors — most refusals are a role, a plan limit, or a version conflict.

Updated

Was this page helpful?