Reporting as a live view

A report opens as rows you can inspect, not as a file you must order before you can see the answer. The live view is paginated, sortable and scoped to the reader. Export and scheduling remain available as the closure of looking.

One evaluator for view and file

Saved views and reports share the configured-view evaluator. The selected kind, filter, columns, reader scope and masking rules determine both what appears on screen and what can be exported. Reporting does not maintain a second query that can silently drift from the view.

The current reporting vocabulary includes identity-governance rows such as grants, decisions and effective permissions. Object references in cells carry their identifiers so supported rows can drill into the governed object.

Reader scope and masking

Opening a report applies the reader's scope. A manager and an administrator can open the same definition and legitimately see different rows. A restricted reader does not gain broader access because somebody else created or scheduled the report.

Field visibility also applies to exports. A masked column is removed from the file rather than merely hidden in the browser.

Export caps before the click

Before export, the platform evaluates the current result and reports:

• the number of rows selected;
• the cap for each available format;
• whether the current result fits;
• whether a format would truncate.

Viewing is paginated rather than capped. Export limits control file generation, not what an authorized reader may inspect.

Schedules and delivery

A saved report can retain its export and schedule workflow. The report definition still owns delivery configuration, while the live view owns inspection. Point-in-time output remains evidence of what the evaluator returned for that run; it is not a permanently live link.

Current limits

• The live report catalogue, open-as-list experience and export/schedule closure are shipped.
• A universal live configuration rail is not yet present on every report view.
• Summary mode is not yet a general reporting primitive.
• Do not infer that a delivered file remains current after its run.
• Delivery history should be read per recorded run; do not claim transparent resend or exactly-once delivery.

See workbench lenses, evidence and signing and API reference.