How to choose a task page
Start with the artifact. If you need a document with sources, choose research or the literature review. If you need a table, choose invoices or the knowledge base. If you need software, choose the internal tool page.
Then check the boundary section on each page. It lists what the workflow does not do, which is usually the fastest way to decide whether the page matches your case.
What every page includes
Each page opens with a short answer you can read in under a minute. It then gives the steps, the preparation, the failure modes, and the checks that keep the output honest. The FAQ answers the questions people ask before they start.
The pages link to the related guide when you need the mechanics, and to adjacent tasks when the job changes shape. Nothing here assumes you already know the product vocabulary.
A note on scope
These are workflows, not promises of complete automation. The pages say where a person still reviews, signs in, or decides. That boundary is deliberate: the output is more useful when you know what to check.
FAQ
Where should I start?
Start with the artifact you need: a sourced report, a table, a mailbox routine, or a small tool. Pick the page that produces that artifact.
Do I need to know the product first?
No. Each page explains the workflow in plain language and links to the mechanics only when you need them.
Are these workflows product features?
No. They are ways of working. Some steps use Sigla, and some steps are yours to check or approve.