All documentation
How the room works
Building on your machine
Models and keys
Tickets, projects and teams
Everywhere else
Getting more out of it
Documentation
What LetThemBuild is, the ideas it is built on, and how to do the work. 30 pages, in the order they are worth reading.
Looking for the answer to one question instead? The help centre is searchable. Building against the API? The developer reference has the routes.
Start here
What this is, how to get it, and how to run your first discussion.
How the room works
The ideas everything else is built on: seats, rounds, agreement and evidence.
- Seats, the lead and the reviewersWho speaks, in what order, and which one is allowed to change your files.
- Rounds, agreement and the final answerHow the room converges, what happens when it does not, and how to give it more room.
- Depth: how hard the room worksFour presets that set how many seats take part and for how long.
- Evidence: verdicts, receipts and findingsWhat makes a review here worth more than an opinion, and how to read it.
Building on your machine
The desktop app: workspaces, what the room is allowed to touch, and git.
- Workspaces and projectsWhere a discussion works, and how to keep several pieces of work apart.
- What the room is allowed to doFive modes, from read-only to unattended, and the approvals in between.
- Git: branches, commits and pull requestsThe repository strip, and the next real step rather than the last one.
- Watching and checking the workThe workbench, the terminal, and how to satisfy yourself it is right.
Models and keys
Who sits in the seats, whose account pays for them, and how to change either.
Tickets, projects and teams
Every discussion is a piece of work you can track, assign and share.
Everywhere else
The web app, the iPhone app, and driving your Mac from either.
- Audit events: runsThe contract behind the audit webhook, the auditor pack and the OpenTelemetry export, generated from the code.
- Audit events: approvals and refusalsThe second page of the audit catalogue: questions asked before acting, refusals, and outside material treated as data.
- Audit events: seats and the networkThe third page of the audit catalogue: the seats, the servers they reach for, and the hosts a run touched.
- Audit events: seats and workThe third page of the audit catalogue: seats and the record of the work.
- Audit events: the teamThe fourth page of the audit catalogue: what changed on the team itself, the policy, the domain, budgets, tokens and the pause.
- Web and iPhoneThe same account and the same discussions, wherever you are.
- Run on my Mac, and watching it liveStart work from your phone, watch it happen, and answer its questions from there.
- The command line, editors and automationDriving the same engine from a terminal, an editor, a schedule or another program.
Getting more out of it
The things that make a long week easier: memory, skills, attachments and what you can do with an answer.
Reference
Plans and money, the keys on your keyboard, privacy, and how to reach a person.
- The brief's changelogWhat changed in the standing instructions every seat is sent, and when; each receipt names the version it ran under.
- Plans, credit and what a month costsWhat each plan gives you, and how the money actually works.
- Keyboard shortcutsThe ones worth learning, on the desktop app.
- Privacy and what leaves your machineWhere your code goes, where it does not, and what we keep.
- Getting help, and telling us when it is wrongThe help centre, support, and what the thumbs under an answer are for.
Start at the top
If you have five minutes, read What LetThemBuild is and Evidence. Between them they are the whole argument for the product.