Exporting your workspace

You can take a complete copy of your workspace at any time: every record, the audit trail and the files your records point to, in one ZIP archive of plain JSON and original files. Every plan includes it. A plan limit never blocks an export, so your data is never held hostage.

Making an export

Owners go to Admin → Exports and choose Start an export. The export is built in the background and the page updates on its own. Earlier exports lists each one with when it was requested, its size, who asked for it and how long it stays available:

You are notified when it is ready or if it fails (Notifications), so you can leave the page. One export is built at a time: while one is queued or being prepared, the button reads An export is being built… and waits for it.

A ready export can be downloaded for 7 days, after which it shows Expired. Request a new one any time; each export is a fresh copy of the workspace as it was then.

What is in the archive

README.md               what each file is
organization.json       the workspace itself
tables/<table>.json     every row of each workspace table
audit-trail.json        every audited change, oldest first
files/<source>/…        files stored outside the database
generation-log.json     how the archive was made

• Tables: every table that holds your workspace's data, including tables that new parts of the app add later, without anyone having to list them. Rows are in a fixed order, by their key:
  • timestamps are ISO 8601 in UTC;
  • binary values are \x hex strings;
  • map shapes are GeoJSON.
• Audit trail: who did what, when, and what changed, for every change ever made in the workspace.
• Files: the bytes your records point to. Today this means files/sources/<document>/, the original file of each document you uploaded or fetched privately, plus its extracted text. Briefings, documents and other generated files will join in later releases.
• Generation log: when the archive was made, and the row count and SHA-256 checksum of every file. If a record points to a file the store no longer has, the log lists it.

Everything is read in one consistent snapshot, so the files match the tables exactly, even if people keep working while the export runs.

What is not in it

• Public records that every workspace shares, such as governments and districts, and published meeting agendas. They are not yours to export, and they remain available from their public sources. Your own links to them, notes on them and private copies are included.
• Names and email addresses of members. These live with the sign-in provider; in the archive, people appear by their account ID.
• Records of the people who run the platform, which are about the service rather than your workspace.

Security

• Only owners can request, list and download exports.
• Downloads come straight from the service to a signed-in owner; there is no public link to forward.
• Every request and every download is recorded in the audit log.
• The archive's size is recorded as usage, under Admin → Usage and spend.