Start here
Pick the row that matches your job. Each page lists tasks in the words people actually use ("a customer cannot log in", "I need to close the month") and links the page that answers it. Nothing here explains a feature from the beginning; that is what the links are for.
| You are | You do | Start at |
|---|---|---|
| Owner | Own the business: contracts, margin, month close, who has access | Owner tasks |
| Admin | Own the workspace: people, boards, SLA, email, portal, automations | Admin tasks |
| Technician | Work tickets, run a service day, move stock, log billable time | Technician tasks |
| Operator | Run the instance: stand it up, back it up, upgrade it, watch it | Operator tasks |
| Agent author | Wire an AI agent, script or plugin against Marula | Agent tasks |
Two pages cut across all five:
- Troubleshooting starts from a symptom, not from a feature.
- Glossary defines the vocabulary these pages assume.
If you are a client of an MSP rather than a member of its team, skip to Portal client tasks. The rest of this page assumes staff access.
How these pages are built
Every entry names a task, then links the page that answers it. Where a task has no page yet, the entry says so under Not documented yet instead of describing behaviour that does not exist. That list is the backlog for whoever writes docs next.
The pages are not arranged by product menu. A task such as "a customer cannot log in" crosses settings, email, the portal and the auth flow, and the entry sends you to each part in the order you would check it.