> ## Documentation Index > Fetch the complete documentation index at: https://docs.bumara.com/llms.txt > Use this file to discover all available pages before exploring further. # Find your way around > The layout of Bumara — the dashboard, the sidebar, workspaces, and the patterns that repeat everywhere. Bumara looks the same wherever you are, which means learning one screen teaches you most of the others. This page explains the layout and the handful of patterns that repeat throughout. ## The dashboard Your landing screen answers three questions at a glance: | Panel | Answers | | ------------------- | ----------------------------------------------------------- | | **Money** | What is owed to you, what is overdue, what came in recently | | **Obligations due** | What must be filed, and by when | | **At risk** | What is close to a deadline, blocked, or waiting on you | | **Today** | The specific items assigned to you right now | The dashboard is deliberately short. It is designed to be read on a phone in under a minute, several times a day. ## The sidebar The main sidebar groups Bumara by what you are trying to do: | Section | Contains | | -------------- | ------------------------------------------------------------------ | | **Dashboard** | The overview above | | **Compliance** | Obligations, filings, tasks, documents, service requests, timeline | | **Regulators** | One workspace each for PACRA, ZRA, NAPSA, NHIMA | | **Invoicing** | Sales, purchases, payments, products, reports, settings | | **Payroll** | Employees, monthly inputs, pay runs, loans, returns, reports | | **Inventory** | Items, stock operations, sales, expenses, insights | | **Settings** | Organisation, team, notifications, plan and billing | You only see sections your role allows and your plan includes. If a section is missing, check [Team and roles](/account/team-and-roles) first, then [Plan and billing](/account/plan-and-billing). ## Regulator workspaces Every regulator has the same workspace, so once you know PACRA you know ZRA: | Page | What is there | | -------------------- | -------------------------------------------------------------- | | **Overview** | Active obligations, open filings, next due date, task progress | | **Obligations** | The recurring things you must file with this regulator | | **Filings** | One entry per period — the actual submissions | | **Service requests** | One-off jobs, such as a name change or a registration | | **Tasks** | Every outstanding task across this regulator, in one list | | **Documents** | Everything filed with or received from this regulator | | **Timeline** | The full history of activity | | **Authorisation** | Your named representative for this regulator | If you have not connected a regulator yet, its workspace shows a **Connect** prompt instead. See [Set up your business](/start/set-up-your-business). ## Patterns that repeat everywhere ### Draft, then commit Almost nothing in Bumara takes effect the moment you create it. Invoices start as drafts. Pay runs start as drafts. Stock adjustments start as drafts. You create, review, then take a deliberate second action — send, approve, post — that makes it real. This means you can always prepare work safely and check it before it counts. ### Status tells you where something is Every record carries a status, and the status controls what you can do to it. A draft invoice can be edited or deleted; a sent one cannot. A posted stock adjustment cannot be changed, only reversed. See [Statuses explained](/help/statuses) for the full list. ### Checklists gate submission Filings and service requests carry a checklist of tasks and a list of required documents. You cannot submit until the required ones are complete. Bumara shows you exactly what is outstanding rather than simply refusing. ### Everything is attached to something Documents attach to filings. Payments attach to invoices. Evidence attaches to findings. There is no loose pile of files — every document sits against the record it belongs to, which is what makes an audit survivable. ### Nothing is quietly deleted Corrections happen by adding, not by erasing. A wrong invoice is voided or credited, not deleted. A wrong stock movement is reversed, not removed. The original stays visible so the history holds together. ## Finding things | To find | Use | | ------------------------------------ | ---------------------------------------------------------------- | | A specific invoice, employee or item | The search box at the top of the relevant list | | Everything due this month | Compliance → Filings, filtered by due date | | Everything assigned to you | The **Today** panel on the dashboard | | What happened to a record | The **Timeline** tab on that record | | A certificate or acknowledgement | [Document vault](/account/document-vault), filtered by regulator | | Why something is blocked | Open the record — blockers are listed at the top | ## On your phone Bumara works in a mobile browser. The layouts that matter most on a phone are the dashboard, approvals, notifications, and the till. Long data entry — bulk employee imports, monthly payroll inputs, stock counts across a warehouse — is easier on a laptop. Ready to work? Start with [Compliance overview](/compliance/overview), which explains the obligation, filing and task model everything else builds on.