Reports registers recurring or on-demand reporting operations with ownership, scope, audience and execution settings.
A report can be managed as a configured operation. A report here is a registered, governed operation: scheduled or on-demand, sandbox-testable, secured by your organisation's rules, and traceable to its run. This manual covers the report registration, its lifecycle, and its wiring.
What you record
The report registration
| Field group | What it holds |
|---|---|
| Identity | Name, description, the icon, the module it reads, the analytics type |
| Placement | The categories and tags it files under, the display order, the visibility |
| Lifecycle | Status, enabled/schedulable/exportable/shareable flags, the owner |
| Governance | The security expression (who may see it) and the audience expression (who it is for) — your organisation's rules, applied to the report itself |
| Scope | The entity type scope, the business era classification, the category classifications |
Two properties carry most of the weight:
Sandbox-testable. A report with a configured sandbox execution path can be run in that mode — the change tested before it becomes history. Use that path to check a new configuration before enabling its live schedule.
Governed by expressions. Who may run a report, who receives it, who sees its results — these are your organisation's security and audience rules, applied to the report as data, not as a distribution list maintained by hand.
The run
Inspect the available run records: what ran, when, who requested it, what it produced. The moment you ask where did this number come from? — the answer is the run, traceable in your deployment.
The bindings
A report binds to the processes it measures — the report-process binding that makes "a report is a process" literal: the report's execution is a governed operation like any other, and its output can feed the processes that need it.
What you can do
- List, search, filter — the report registry by category, module, status, visibility
- Run — on demand or on a schedule you set; inspect the available run history
- Sandbox-test — run the configuration before it goes live
- Export & share — per the report's own governed flags, within your rules
- Relate — the wiring below
What it connects to
| Target | Examples of the connection |
|---|---|
| Categories & tags | The filing structure your operation defines |
| Other reports | Related readings, predecessor/successor chains |
| The processes it measures | The report-process bindings |
| The owner | The person accountable for the reading |
Where it feeds
Reports are the body reading itself: cross-module measures, the semantic layer's governed definitions, the readings presented through the offerings. The report-is-a-process story is the platform page; this manual is the working surface — and the security and audience rules need to be checked across execution, display, export and sharing.
The pattern note: same four-part structure — record, do, connect, feed. The reports manual is where the provenance pattern completes: not only does every number trace to records, every reading operation traces to a governed, owned, scheduled run.
Implementers stand up your first reports on the process substrate at adoption and configure the semantic layer — what your terms mean; consultants help define which measures your organisation actually governs by.
No record is an island
A report relates to the modules it measures, the categories that file it, the owner accountable for it, the processes it feeds. The reading is part of the graph — which is why "which reports fed this quarter's numbers?" answers from the wiring, not from a folder of dated exports.
Review the record and its context before deciding what to do next.
Venues → · Employees → · All manuals → · The Reports platform page →
Check your work
Confirm the source, period, calculation and intended audience. Where the configured report supports a sandbox run, inspect that result before enabling a live schedule. Check access to the exported file as well as to the report screen; sharing a result can create a separate copy with its own responsibilities.
Available screens and actions depend on your deployment and permissions. Use this manual alongside the configured workflow and the capability demonstration for your installation.