Skip to main content
Reports (/compliance/reports) is where evidence becomes a document you can hand to somebody. It lists every report the workspace has generated, and it is where you create new ones. There are two report engines behind this page, and they answer different questions.

​
Compliance reports

​
Scope, framework, depth

1

Pick a scope

A single dataset, a set of datasets, or the entire workspace. The smaller the scope, the faster the build.
2

Pick a framework

One of the six standards. What each mapping does and does not claim is on Frameworks, and every generated report carries that framework’s applicability conditions on its face.
3

Pick a depth

4

Set a time window

Activity, scans, and healings inside this window appear in the report. Pick a quarter for a quarterly review, or the whole workspace lifetime for a first-time audit.
5

Generate

The report is built and appears under Reports with a download link.
Use Summary for weekly check-ins, Detailed for monthly reviews, and Exhaustive when an auditor asks for source material.

​
All six frameworks at once

The Frameworks table needs a readiness figure per framework, and generating six separate reports to get them was slow: almost all of the cost is framework-independent evidence assembly, repeated six times. POST /api/compliance/report/frameworks builds the evidence once and applies every framework profile to it. Each entry carries the same control-mapping shape a single-framework report returns. Use it when you want comparable readiness figures. Use POST /api/compliance/report when you want one document for one framework, which is what an auditor actually receives.

​
Compliance report API

All of them need compliance.access.

​
General reports

The /api/reports engine covers everything that is not framework mapped: ad-hoc documents, project reports, and scan-scoped exports. A report is created from a name, an optional template, a scope (project_id, dataset_id, or a list of scan_ids), a format, and an optional list of sections. Generation is synchronous and the report lands with a status, a progress figure, a file size, and a content summary you can inspect before sharing.

​
Report templates

Templates standardize how reports look across the team. A workspace template covers the whole tenant; a project-level template can override it for one project. Mark a project-level template as default so every new report in that project starts from it.

​
Export templates

Separate from report templates, export templates define reusable CSV and JSON exports of scan results: which columns, which filter, which sorting. Edit them at /reports/exports/templates and apply them from any scan’s Export menu. Export templates are gated behind FEATURE_ADVANCED_EXPORTS, which is a different license flag from FEATURE_COMPLIANCE_REPORTS.

​
Sharing

  • Every generated report has a stable download link.
  • HTML reports can be opened by anyone holding the link. Treat the link like a secret and rotate it by regenerating.
  • Compliance reports include a content summary so you can confirm what is in the document before sharing it.
  • Generation, download, and deletion are all written to the audit trail.

​
Common workflows

  1. Confirm which trust services categories your engagement covers. The mapping means different things for a Security-only scope.
  2. Make sure every dataset in scope is in a single project.
  3. Generate a SOC 2 / Detailed / PDF report scoped to that project, with a time window covering the audit period.
  4. Generate an additional SOC 2 / Exhaustive report as source material in case the auditor asks.
  1. Generate a Summary report at workspace scope every Monday via a scheduled report.
  2. Share the link in your weekly channel.
  1. Select all six frameworks on Frameworks.
  2. Read the readiness table, which builds evidence once and applies all six profiles to it.
  3. Read each figure next to its “not assessed” count, never alone.
  1. Generate an ad-hoc Detailed / PDF report scoped to the training dataset.
  2. Attach it to the model card.

​
See also

Frameworks

What each standard’s mapping covers.

Data posture

The evidence a report is built from.