Export Data Dialog

About this block

Export Data Dialog lets workspace admins pull the Acme workspace, not their personal account, as a download. Two format radio rows sit at the top: CSV one file per table, 6 files zipped together and opens in any spreadsheet; and JSON one file, the whole workspace as a single machine-readable file. Three scope checkboxes follow: all 12 projects with settings and deploy history, 14 members with roles and join dates, never passwords, and the audit log at 8,214 entries back to Jan 2024, unchecked by default. A muted callout then delivers the timing honestly: the export lands by email within minutes, usually under 5, not the 30 days the statute allows, the same pipeline as the account export.

Formats and scopes are separate arrays above the component, with real counts in the descriptions. The timing callout reuses statutory language precisely because that is what anxious users search for.

When to use

Reach for this block on the workspace settings data page or as a secondary action on the billing page. Wire the export button to your data-export job API, send the download link by email, and update the scope counts from your live workspace metadata endpoint.

A natural flow around it on an Application Pro page:

Before

• Settings page
• Billing page

After

• Activity feed
• Notifications

What you can display

One strong use is workspace-level GDPR or ops export. Other export dialogs:

• Single table export. No scope section, just the format radio and the timing callout for one dataset.
• Date-ranged export. Add a date range row between format and scope to slice audit logs by period.
• Per-project export. Scope checkboxes become the project list, each with its size shown in the label.

Tip: name the timing in minutes, not just "soon", users with statutory obligations read the callout before they click and the specificity earns the trust.