Access and permissions in Reports
A report appears and runs only when all four layers allow it.
Reports permissions
| Permission | Allows |
|---|---|
reports.view | Open Reports, see the catalogue, run reports on screen, save filters |
reports.export | Download Excel or PDF, queue exports, see Export history, create schedules |
Without reports.view (or with the Reports module off) you see Reports unavailable: "Reports require
tenant enablement and reporting permissions."
Each report's own permission
You also need the permission for the data, the same one you'd need in the source module. See The report catalogue for the full list. For example:
| Report | Also needs |
|---|---|
| Trial balance | Accounting module, accounting.report.trial-balance.view |
| Sales by customer | sales.invoice.view |
| Stock position | inventory.report.stock.view |
A report you can't run is simply not listed.
Business units
Reports include only your active, assigned business units.
| You choose | Report includes |
|---|---|
| No unit | All your assigned units |
| A unit ID | That unit, if assigned to you |
- No assigned units: "Report business unit access denied".
- Access is checked again when an export runs. If your access changed between queuing and running, the job fails with "Your access changed. Create a new export."
Example roles:
| Person | Permissions |
|---|---|
| Nadia | reports.view, reports.export; all accounting report permissions; sales.invoice.view; purchase.invoice.view |
| Omar | reports.view; purchase.invoice.view; inventory.report.stock.view |
| Farah | reports.view, reports.export; accounting.ar.aging.view |
Omar can run Purchases by supplier on screen, but has no Excel button: he lacks reports.export.
Next: The report catalogue.