Data Export

The Data Export page lets admins generate downloadable archives for compliance, backup, or analysis.

Configuration

Group by

How rows are aggregated:

Organization — A single row per time period.
User — One row per user per time period (great for usage analysis).
Department — One row per department per time period.

Projects (scope)

Which areas to include:

All data
Chat
Files
Meetings

Choose more than one if you want a wider view, or narrow to a single project for cleaner CSVs.

Time range

Start and end dates — the period to include. Use the calendar pickers.

Time interval

How data is bucketed within the range:

1 day — One file per day (UTC).
1 month — One file per calendar month (UTC).

Pick monthly for compact archives; pick daily for granular analysis.

Running an export

Click Start export. The job goes into a queue and runs in the background. You can leave the page — you'll get a notification (and email, if enabled) when it's ready.

While an export is running, the Start button is disabled to prevent overlap.

Export history table

Below the configuration:

Requested — When the export was kicked off.
Status — Pending, Processing, Completed, Failed, or Expired. Hover Failed for the error.
Settings — A summary of the configuration used.
Expires — When the download link expires.
Download — Only shown for completed, non-expired exports.

Download links expire after a set period — typically 7 days. Re-run an export if you need it again after expiry.

Failed exports

If an export fails, the error message explains why. The most common causes are too-large date ranges or transient backend issues. Try a narrower range or wait a few minutes and re-run.

Audit

Every export is also recorded in the audit log for compliance.