Every automated process starts life as a page of notes: the steps someone follows, the exceptions they've learned to watch for, who to call when it breaks. That page usually lives somewhere else, in a wiki nobody updates or a doc in one person's drive, and it drifts away from what the workflow actually does.
Lodol now has Documents, so the write-up can live right next to the workflows that run it.
In the same place as your workflows
Choose Create and then New Document on the Workflows page. Documents sit in the same list as your workflows and in the same folders, so the runbook for month-end close can live in the Month-end folder beside the workflows that do the work. Anyone who opens the folder finds both the process and the explanation of it.
Quick to write
The editor has what a working document needs: headings, bulleted and numbered lists, checklists, quotes and dividers, bold, italics, links, highlights and inline code. Notes you already keep in Markdown can be pasted straight in, and their headings, lists and links arrive formatted. There's no save button, because everything saves as you type.
Earlier versions, side by side
Documents keep a version history, just like workflows. Open it to compare an earlier version with the current one, side by side, and choose Restore This Version to bring it back. Restoring adds a new version instead of erasing the ones after it, so even a restore can be undone. A rewrite that went wrong is an undo, not a lost afternoon.
Share it without sharing your workspace
Some documents are for people outside the team: the contractor who covers month-end, the auditor who wants to know how bills are approved. Share turns on a link, and anyone with it can read the document. They can't edit it, and they won't see anything else in your workspace. The link always shows the latest version, so nobody reads a stale copy, and Make Private turns it off whenever you like.
And when a document needs to leave Lodol altogether, Export saves it as a PDF or as Markdown.
What teams use it for
- Runbooks. What a workflow does, what it needs before it runs, and what to do when it stops.
- The policy behind a workflow. The expense policy in the same folder as the workflow that checks receipts against it, so whoever changes one finds the other right beside it.
- Checklists for the human steps. The parts of month-end no workflow does, ticked off as they're done, next to the parts that run themselves.
- Handover notes. Everything a new teammate needs to take over a process, in the folder they'll be working in.
Documents are available on every plan, and the same permissions that decide who can edit your workflows decide who can edit your documents.
Write down the process you just automated.
On the Workflows page, choose Create, then New Document. Start free if you don't have a workspace yet.
