Board plus documents

Where does the writing
about the work live?

A ticket says what to do. It is a bad place for why. So the brief goes in a doc, the decision goes in a chat thread, the runbook goes in whatever the last person used — and six months later the ticket is still there and the reasoning is gone.

14-day trial · £2.49 per seat per month · viewers are free

THE DRIFT

Two tools, two lists
of who can read.

The cost is not the second subscription. It is that the two halves are governed separately, and they only have to disagree once.

  • Access decided twice

    Someone joins and is added to the board. Nobody adds them to the docs. They spend a fortnight asking questions that are already written down, or worse, guessing.

  • Offboarding that half-happens

    Someone leaves and loses the board. Whether they lost the documents depends on whether the person doing the offboarding remembered there were two systems.

  • The thread that was the decision

    The reasoning is in a chat message from a Tuesday, findable only by someone who already knows it exists. That is not a knowledge base, it is an oral tradition.

WHAT LAVER DOES

One workspace,
one membership list.

The wiki belongs to the workspace, not to a board. Access is decided once, and both halves stay in step because there is only one list.

  • A tree of pages, searchable

    Nested pages with history and attachments, and full-text search across all of them. The brief, the runbook and the reason you chose the thing you chose sit beside the tickets that came out of them.

    Wiki pages
  • Add someone once

    A workspace member can read the wiki. There is no second permission model to keep in step, and no way to be on the board but locked out of the writing about it.

    Roles and permissions
  • Remove someone once

    Deactivating a member removes both halves at the same moment — and it disables any API keys they issued, so an agent they set up stops with them.

    Offboarding

HONEST FIT

One list cuts both ways.

The thing that makes this simple is also its limit, and it rules some teams out.

A good fit when

  • Everyone with a login is a colleague, and everyone should be able to read the same things.
  • The writing you care about is briefs, runbooks and decisions — not a public help centre.
  • You have been meaning to consolidate two subscriptions into one.

Not what this is

  • No page permissions. Every workspace member can read the whole wiki. If some pages must be restricted, Laver cannot do it.
  • No public sharing and no anonymous view of anything — every reader needs a login.
  • No comments on wiki pages, and no real-time co-editing.
  • Not a document editor and not a spreadsheet.

READY WHEN YOU ARE

Put the why beside the what.

Every workspace comes with a wiki already in it. There is nothing to connect and nothing to keep in step.

Start your free trial

Keep reading