Who can export
Only a team Owner or an organization owner can start an export and download it. An organization owner sees the card even when their team role is Admin. Admins, Standard Users, Viewers, and Security Reviewers do not see the card. The server applies the same rule. API tokens cannot start or download an export.Start an export
- In the sidebar, click Team Settings.
- Scroll past the team card to the Export team data card, near the bottom of the page.
- Click Start export.
Limits
- One export runs at a time per team. While one runs, Start export is disabled.
- A team can start at most 5 exports in 24 hours.
- An export that runs for 12 hours stops and shows Failed.
- If an export fails, start a new one. If it fails again, contact support with the export ID shown on the card.
Download link and retention
- Each click on Download creates a new download link. The link works for one hour.
- Corridor deletes the ZIP 7 days after the export completes. The status then shows Expired, and the ZIP cannot be downloaded. Start a new export to get current data.
What the ZIP contains
The ZIP holds the CSV files below and amanifest.json file. Each CSV file starts with a header row. Dates are ISO 8601 in UTC.
There is no option to choose a time range. “All time” means every row the dashboard shows, at any age.
The export is not a snapshot
Corridor reads each file in turn while the export runs. Data that changes during the export can be in one file and not in another.findings.csv,pr_reviews.csv, andmcp_servers.csvhold only rows created up to the moment you clicked Start export.projects.csv,members.csv,guardrails.csv, anduser_compliance.csvhold what is stored when the export reaches that file. They can include rows created after you clicked.pr_review_comments.csvandpr_review_findings.csvhold every comment and finding of the reviews inpr_reviews.csv. A comment or finding added to an older review after you clicked can be included.
Feature flags
Some data shows in the dashboard only when a feature is on for your team. The export follows the same settings:- If AI authorship is off for your team,
pr_reviews.csvhas noai_generated_percentagecolumn. - If duplicate detection is on for your team,
findings.csvandpr_review_findings.csvleave out findings marked as duplicates, as the dashboard does. - If your team does not see Bugcrowd findings in the dashboard,
findings.csvhas none.
Files and columns
projects.csv
Every project of your team, except projects that are being deleted.
members.csv
The members shown on the Teams page. Service accounts are not listed.
guardrails.csv
The guardrails of every project, as the project guardrails page shows them. Archived guardrails are included. Guardrails of projects that are being deleted are not.
Each row names its project, as the team guardrails page does.
findings.csv
The findings shown on the Findings page, at any age. Findings that Corridor’s AI closed as false positives are not included, as on the Findings page. A finding closed by Corridor’s false positive review is included. While a project is being deleted, its findings are left out, as in projects.csv.
pr_reviews.csv
The PR reviews shown on the PR Reviews page, at any age. Reviews that failed to post are not included.
pr_review_comments.csv
The comments of the PR reviews in pr_reviews.csv.
pr_review_findings.csv
The findings raised in the PR reviews in pr_reviews.csv, as the PR review page shows them. The file uses the same state and duplicate rules as findings.csv. Four things differ:
- Findings that Corridor’s AI closed as false positives are kept, as on the PR review page. For those rows,
false_positive_reasonsays why. - Findings of every source on those reviews are kept, including Bugcrowd.
- There is no date cutoff. A finding added after you clicked Start export is here when its review is older.
- Findings of a project that is being deleted are kept.
findings.csvleaves them out while the deletion runs.