Report view
What the Screen Is For
Present a report using the viewer’s access and expose permitted editing, sharing, printing and recurring delivery.
What It Shows and Lets People Do
The view renders the stored kind and narrows source execution through supported parameters. Save and Save As retain their distinct ownership behavior. Sharing, rendering and scheduling use their implemented grants, including the separate schedule-use console gate.
States and Errors
The report can be visible while its source execution fails. Removed or hidden presentations use the unavailable state. Save conflict, source changes and sharing refusal require deliberate resolution.
Patterns It Must Respect
The existing report-specific layout supplies its header, sharing and copy dialogs and export controls. Rendering uses the print workflow rather than issuing unrestricted browser API reads.