Platform

Platform overview How it works Authorization testing Evidence & reports Private scanning Integrations

Solutions

Security agencies Product teams Regulated industries Partner programme

Learn

Blog Knowledge hub Compare

Resources

Pricing Documentation Help centre FAQ Security & data What we haven’t proved

Company

About Contact Careers Sign in to the platform Start a $199 pilot →

Home / Help centre / Team & access

Team & access

Why can't I export findings?

Quick answer

Exporting findings needs the issue:export permission. If the Export JSON or Export CSV buttons on Issues fail or do nothing, your role lacks it. Ask an admin to add it. The PDF report has its own key, scan:read_report.

Why this happens

Exports carry data out of the app, which is why each export has its own permission, separate from the key that lets you read the same data on screen. Reading findings is easy. It needs issue:read. Exporting them needs issue:export. A role can hold one and not the other.

How to fix it

  1. Open Issues.
  2. Set the search and filters you want. The API Reference says the export takes the same filters.
  3. Click Export JSON or Export CSV. Both buttons live on the Issues page, alongside the search box and the triage chips, and the file comes down to your browser as a download.
  4. If nothing downloads or the app refuses, ask an admin to add issue:export to your role. Say which filters you used, so they can test the same export.
  5. Need a document for people outside the tool? Open a scan and use Download report, or use the Report action on Recent Scans.

Each export has its own key, so check the one that matches what you want. The targets list export needs target:read. The PDF report needs scan:read_report, so a person can hold the report key and still be unable to export raw findings. The sitemap export on a scan page is separate again, and it sits in the scan detail view.

Still not working?

  • A file that opens but looks short? Check your filters and whether the triage chips on Issues are hiding statuses. Read why a CSV export looks partial.
  • Does every export fail? An admin can read your role and tell you why.
  • For the full routine, see how to export findings.

Send us your role and the button you clicked through the contact page if the problem stays.

Full tutorial

How to export vulnerability findings to CSV or JSON

Step-by-step, with annotated screenshots.

Updated · Back to the help centre

Still stuck?

Tell us what you see on screen and an engineer will help you sort it out.