Export
What It Is
An export is the retained record of producing information as a file. For an everyday question, it means writing the complete result to CSV or Excel rather than reading one page on screen. For a report, it means rendering the presentation to PDF or a supported workbook. A schedule adds a timetable and recipients so that file production and delivery can happen without someone remembering to request each run.
The broadest planned form is the complete workspace data package. That form has its own settings, destinations, coverage declarations and execution history. Its foundation currently accepts requests and records them, but completed package generation and delivery remain unfinished. This distinction is part of the product description, because a queued execution does not establish that an administrator can already retrieve all the organization’s data.
Each export has an identity independent of its source query or report. It records the request and eventual result, including file availability. A completed file can remain useful after its source presentation is deleted.
What It Is Not
An export does not update the source records or import new records. Those outcomes belong to other data-management work. Monthly snapshots retain application history inside Rhythm and serve a different purpose. Some report downloads are created directly by the browser; those are separate from Platform’s rendering record. File delivery also deserves its own access discussion: a personal link enables a recipient to retrieve the generated copy even though query generation checked the acting person’s access.
How It Is Used
Staff export results for spreadsheet work and prepare report files for colleagues. A person requesting production must be permitted to execute its source. Workers recheck access before generating the file. Scheduled work refreshes the owner’s access, while Run Now follows the person pressing the action. Lost access can stop delivery and pause responsibility until a manager takes over.
Recipients receive separate messages and links. Run history helps an administrator distinguish a failed source execution from a missing or skipped recipient. A retry must avoid sending the same run to the same person again. Retained files, short-lived storage redirects and personal delivery links have different expiry periods.
Its Facets
Query export. The writer consumes the full result in its declared order and preserves useful value types and safe spreadsheet text.
Report export. A controlled browser renders the console print page with the requester’s access and bounded file production.
Schedule. Query schedules retain a source copy; report schedules render the current report. Timetable, template and ownership explain what unattended work does.
Recipient and delivery link. Users and permitted outside addresses receive personal links, with current recipient membership checked before retrieval.
Run history. Execution and delivery outcomes provide an accountable record of what happened rather than only the next scheduled time.
Workspace data export. Dedicated administration protects broad portability and records destination widening. The complete package remains a delivery objective beyond the implemented admission foundation.
Retention. Generated query and report files remain for thirty days. Workspace package settings permit shorter configured retention.
How It Relates
Queries and reports define sources. Communications owns templates and message submission. Security provides refreshed access, integrations own destination connections and licensing supplies future package allowances. Export dependencies also help explain why deleting a report and deleting its completed file are different actions.
What It Could Become
The product should finish the already decided package controls, including recent authentication and workspace allowances, before treating complete portability as available. A personal recent-export list is another possible extension. Any new delivery format should retain accountable execution, explicit expiry and recipient-specific access.