Exports
Take it out the way you were reading it.
The rows you picked, the columns you left showing, the pages you actually need — as a spreadsheet, a document, or paper. Nothing to reconstruct on the other side.
The problem
Most exports hand back the whole table.
You spent ten minutes filtering to the eleven people who need a letter, and the download gives you four hundred rows and every column the object has ever had. The work of narrowing it happens twice.
A spreadsheet of what is on screen.
Export follows the view. Whatever the chips, filters and Fields menu left showing is what lands in the file — because that arrangement was the question you were asking.
The rows you picked
Tick a few and the export is those. Tick none and it is everything the current view holds, which is the same thing you can see.
The columns you kept
Hidden fields stay hidden. A form with sixty questions does not become a sixty-column file because you exported it.
The filter comes too
Completed only, this month only, this programme only — the file is the answer to the question, not the table it came from.
Opens anywhere
CSV, so it opens in Excel, Numbers, Sheets or whatever the person you are sending it to actually has.
The part of the packet somebody asked for.
A twelve-page application where the office wants pages three to five is not a download of twelve pages. Pick the range, take those.
A page range
Choose the pages in the viewer and download or print exactly those, from a file nobody has to split by hand first.
Named groups
If the packet has named parts — the medical form, the consent page — take a group by its name instead of counting pages.
Straight to print
The same selection prints, for the times the answer has to be physical and the office has a tray rather than an inbox.
From a share too
A recipient reading a share link can take the same selection, if you left downloads on.
Your workspace, in one file.
Not for a report — for leaving, for an audit, for the version of your data that outlives whatever tool you keep it in. One JSON file with the objects, their fields, every record, and the lists and who is on them.
Structure and rows
The objects and their fields, so the export explains its own shape rather than being a flat dump somebody has to guess at.
Lists and membership
Who was on which list, which is the part a table of records alone cannot tell you.
Files are listed, not included
Named and addressed, not embedded — a drive is far larger than one response can carry. Said here rather than discovered inside the file.
Before you delete anything
Deleting a workspace removes everything at once and cannot be undone. The export is the thing to take first.
Where the data comes from.
An export is the last step. These are the ones before it.
It is your data. Take it whenever.
The view you are reading, the pages somebody asked for, or the whole workspace — without a support ticket.