Reports

Backed by: the questions it names, each read live from your Worker through its own declared reads. Scopes: whatever each question needs, and none of its own. Plan: Team to run one, Enterprise to save one.

What it answers

Can I send this to whoever asked?

A question answers on its own pane. A report puts several answers in one document, the numbers, the renderings, when they were read and in which environment, for somebody assembling an audit response or a board paper. Revenue integrity, access attestation, now and on a date, and over-grant are the questions a report can name today, what it never stores is what a saved one keeps, and plans and pricing is what each part costs.

Reports sits in the rail’s Compliance group, beside Access, Attestation, Audit explorer, Evidence and Privacy, once an environment is connected.

A report is a definition, run live

A report is a name, a purpose, the questions it names, and a filter state. New report takes a name and a purpose, with every question ticked to start. The shell’s filters in force narrow it, on the axes its questions declare. A question that opens on a range reads that far back when the report names none: over-grant reads the last 90 days, and every other question reads everything kept. The document names that range only when every question in it that takes a range opens on one.

Run report reads every answer from your Worker at that moment, and the document states that time. Run again reads them all again. Each question inside a report still shows only what its own plan allows: where the itemised rows are not on the plan, its section shows the counts and says what itemising buys.

Nothing about a run is stored. The answers go with the screen, unless somebody exports them.

Two exports, both built in your browser

ExportWhat it holds
Export JSON, per questionThat question’s answer verbatim, with the report’s name, the run time, the environment and the filters. Only what the section draws
Print or save as PDFThe whole report: its name and purpose, the run time, the environment, the filter state and every rendering, as a print view your browser saves as PDF

Neither passes through us.

Saving one, on Enterprise

Save definition keeps the report, never its answers. What is kept in our D1 is the name, the purpose, who saved it and when, the questions it names and the filter state, and a run log of when each run happened and who ran it. The log keeps the newest 100 runs per report.

A saved filter state names no subject. An organization or a person is an id read off your Worker, so keeping one would be keeping your data. A report narrowed to a subject still runs, and says to clear the subject before it saves. A range is kept by its length, so a report saved over the last 30 days reads back 30 days from whenever it runs.

A saved report runs the way a new one does: live, from your Worker. Running it adds a line to its log and nothing else. A question the dashboard no longer answers stays in the definition and says so in the document.

Who may change it

Owners and admins save and delete a report, and both acts are audited with the number of questions, never what a run answered. Members run a saved report, and the run is logged under their name.

When the plan stops saving

Saved reports turn read-only, and are deleted thirty days later. The same pass that keeps the privacy history’s window records the lapse, and each saved report states the date it turned read-only and the date it will be deleted. A lapse that is paid before then is cleared.

A frozen report can still be deleted, because taking a definition away stores nothing. Saving and logging a run are what the freeze refuses. On Team a frozen report still runs; the run is not logged.

Closing the account deletes all of it.

On Free and Solo

The pane is drawn locked, and says what Team buys. Each question still answers on its own pane, on every plan, and through your CLI and your Worker’s API. Saved reports frozen by a downgrade are still listed under it, to read and delete.

ESC