Skip to main content
You can export the rows on a records table or a test-result table from the platform. The same Export data control is available in monitoring and in development. In monitoring, you can also export the Users tab, one row per user. To download a monitoring pipeline from the command line instead, use openlayer export. Exports do not include custom columns.

Export records

On Records, or on a test-result table, open the table options overflow and select Export data. The Export data modal explains:
Choose a format for your export. The download will start automatically once the file is ready.
Select Export data to start the export, or Cancel to close the modal. Activity in the platform tracks the job as Exporting data, then Exported data when the file is ready. If the job fails, activity reads Failed to export data. Exporting data requires the Export data permission. Viewers cannot export. See Roles and permissions.

Export users

On Users, select Export users (the download icon) in the page header. The button is disabled while the table is empty. The file has one row per user that matches the tab’s current filters. Filters on totals, such as Total records or Total cost, apply to each user’s totals, so the file has the same users the tab shows. Every file has these columns, whichever ones the table shows: userId, dateOfFirstRecord, dateOfLastRecord, sessions, records, tokens, cost Users exports do not include scores, so the modal has no Scores picker. Activity and the Export data permission work as they do for records.

Choose a format

Pick one format for the file:
  • CSV — Comma-separated values, opens in any spreadsheet tool
  • XLSX — Microsoft Excel workbook
  • JSON — Structured data for programmatic use

Include scores

Under Scores, choose which test scores to attach to the export:
  • No scores
  • All scores
  • Scores for {testName}

When the file is split

The modal notes:
Your data will be split into multiple CSVs, one per batch.
Each batch is its own CSV.