Five paths
The documentation is arranged so that you do not have to read the same material twice. Pick the path that matches your task.
| Path | For | Order |
|---|---|---|
| Understand the product | a new team member | What remo is → Capability map → Product model → capabilities |
| Do a task | an editor, a board owner | Grant access and share a link or search → the instruction you need |
| Look up a fact | an administrator, an integrator | Reference → the table → the "why" link into the model |
| Connect an integration | a technical user | Extensions → Events and webhook → Connect an integration → Events reference |
| Run the installation | an administrator | Deploy → Security → Observability → Backup |
How the sections are built
- Overview answers "what is this and why", without details.
- Getting started delivers a finished result in one pass.
- Product model explains entities, relations, states and permissions. Every other section links into it.
- Capabilities are overview nodes: what it gives, when to use it, what it combines with, where the limit is.
- How-to is step-by-step and grouped by goal, not by button.
- Reference is the only place with exact values: roles, codes, limits, formats.
How to read a long page
Every page has a table of contents and a "Related pages" block. At the end of a page stands the next step of the route. If you want to read everything in order, take the "Understand the product" path: it is assembled as a sequence.
Where to go next
Quick start — a working board in ten minutes.