Getting your data out of Cavuno used to mean subscribers only. Now every table exports to CSV, from the same place on every page.
How it works
- One control everywhere: each table has a ... menu in its toolbar with an Export action, next to the primary button. The same step works on jobs, companies, employers, candidates, job alerts, and the blog tables
- Eight tables: jobs, companies, employers, candidates, job alert subscribers, blog posts, blog authors, and blog tags all export
- Comprehensive files: every export includes the fields you authored plus each row's id, status, and timestamps, so a file is a full snapshot of the table
- Clean round-trip: job, company, and blog post exports use the same field vocabulary as the matching import, so an exported file re-imports without remapping columns
Built for large boards
- Instant for most: typical boards download the CSV right away
- Prepared links for big tables: exports over 10,000 rows switch to a "Preparing export..." state and produce a download link when the file is ready, up to 200,000 rows
- Permission-aware: export requires the table's read permission, which owners and admins have by default
- Safe candidate resumes: the candidates export includes authenticated resume download links, never public file URLs
On the API too
Every dashboard export has a matching endpoint at GET /api/v1/{entity}/export. Pass format=json for an inline response up to 10,000 rows, or format=csv to run an async operation that returns a download URL, the same pattern as the existing subscribers export.
Applications stay with the employer's hiring pipeline and are not part of the operator export. See the Export your data guide for the full details.