What this page is for
Reports lists every report definition your role is allowed to open, grouped under headings such as Dashboard, Sales, Inventory, Tills and shifts, Purchasing, Ledger, Customers, Dining, Kitchen and Exceptions. Each row shows the report's name and a short description, its key on wider screens, the permission it needs beyond the ones your role already has, and which file formats it can export to — or Screen only where it has none.
This page lists only what your role can open. A report your role cannot run is not shown at all, not even its name: seeing a report in this list already means you can open it.
Everyone whose role holds reports.view sees this page, which is the floor for every report. Opening a particular report also needs that report's own permission, named in the Requires column.
How to…
How to find a report
Type into the search box: it matches the report's name, its key and its description. Clear the box to see every report again.
How to open a report
Press the report's name to go to it and choose what to run it on.
If something goes wrong
If your role holds no report at all, the page says so and tells you to ask an administrator to add the report you need to your role.
If a search matches nothing, the page says so and offers a button to clear the search.
Worked examples
Restaurant and bar
The Acacia Grill & Bar's duty manager opens Reports, types takings into the search box, and goes straight to the daily takings summary under Dashboard without scrolling through the whole list.
Supermarket
Tumaini Supermarket's branch manager sees usage-variance in the list under Inventory with its own Requires column empty, because their role already holds stock.view, which the report needs. A column it would otherwise show, the issue cost, stays hidden because their role lacks catalogue.cost.