# Exports
URL: https://docs.clearly-ai.com/docs/exports
Description: Download review content in Markdown, HTML, PDF, Word, CSV, or XLSX, and know what each format contains for auditors versus downstream tooling.
This page is for security engineers, security leads, and compliance staff who need **artifacts outside the Clearly AI UI**: evidence for auditors, attachments for tickets, or structured files for spreadsheets and pipelines.
Clearly AI generates exports **per review** from the review screen. Some review templates support more formats than others (such as CSV/XLSX).
***
## Audit-oriented vs tooling-oriented exports [#audit-oriented-vs-tooling-oriented-exports]
| Goal | What usually works | Why |
| -------------------------------------------------------- | ------------------------------------------ | -------------------------------------------------------------------------------------------------- |
| **Human-readable evidence** (auditor, executive summary) | **PDF**, **HTML**, or **Word (DOCX)** | Narrative layout, headings, tables for table-generation blocks, compliance columns (when enabled). |
| **Editable or merge-friendly narrative** | **Markdown** | Same content as HTML/PDF in most cases; easy to paste into Confluence or Git. |
| **Spreadsheet analysis** | **XLSX** or **CSV** | Rows and columns for filtering and pivoting; must be enabled by the review template |
If you need machine-readable **full** Review state, use the Clearly AI API when it is enabled for your organization. See [API reference](https://docs.clearly-ai.com/docs/api-reference).
***
## Exporting a single review (UI) [#exporting-a-single-review-ui]
**Prerequisites:** You can open the review in the app and it has finished generating.
1. Open the **project**, then open the **review** you want.
2. Click **Export** on the review view.
3. Choose a format. (Note: **Markdown**, **HTML**, **PDF**, and **Word** are always available for standard reviews. **CSV** / **XLSX** appear only when the **review template** enables them (see [Review template schema](https://docs.clearly-ai.com/docs/review-templates/schema))).
[Image: Exporting data dialog box showing several export formats]
*Figure 1. Data export dialog.*
***
### Markdown [#markdown]
* **Content:** Review Template title, **Summary** block (when present), then other blocks in review template order.
* **Question answers:** Heading is the question text; body is the answer text. **Citations are removed.**
* **Table-generation blocks:** Rendered as **Markdown tables** from stored row data.
**Not included:** Review **comments** and **workflow** / **info** / **warning** / **error** blocks (those block types are skipped in the narrative export).
***
### HTML [#html]
* **Source:** Same content as markdown, converted to a **single HTML document** with **embedded CSS** (self-contained file).
* **Diagrams:** **Mermaid** and **Draw\.io** blocks in the Markdown are pre-rendered to **inline PNG** (`data:` URLs) when rendering succeeds, so a downloaded `.html` can be opened offline without the app.
The stylesheet is tuned for **print-like** output (similar to PDF generation). Do not expect the HTML to match the **live review UI** pixel-for-pixel (colors, spacing, and interactive citation UI differ).
***
### PDF [#pdf]
* Same as HTML, printed to PDF.
***
### Word (DOCX) [#word-docx]
* Same as HTML, converted to docx.
* Note: If the review template defines a **Word template** stored for your tenant, the export **fills that template** using answers from **all reviews in the same project** (template variables keyed by block template IDs), plus **project metadata** (name, dates, review stage, requestor name when resolvable).
***
### CSV (review template flag: `special_export: csv`) [#csv-review-template-flag-special_export-csv]
CSV is **not** a full dump of every question. It is built for **tabular asset data**:
1. **Preferred:** Approved asset data recorded on answers.
2. Else **asset identification** answers (Markdown table parsed into rows).
3. Else **`table_generation`** rows mapped into the same column shape.
**Header row (fixed order):**
| Column |
| ------------- |
| `Asset Name` |
| `Description` |
| `Type` |
| `Sub-Type` |
| `Confidence` |
| `Source` |
Asset identification rows **map** into these columns (unused columns are empty).
When the review template sets **`joined_tables_export`**, the UI still triggers export with format **`csv`**, but the download is an **XLSX** (see below), not a `.csv` file.
***
### XLSX (two different mechanisms) [#xlsx-two-different-mechanisms]
**1) Joined tables (`special_export: csv` + `joined_tables_export`)**
* **One worksheet per `table_generation` block** in the **current** review.
* **Sheet title:** The block’s table title from configuration or the question title.
* **Columns:** Always includes **`Asset Name`**, then every other column name seen across joined data, **deduplicated**, in discovery order.
* **Rows:** Merged on **`Asset Name`** across:
* The primary table block, and
* Optional **follow-up** reviews in the **same project** when the block’s `followup_questionnaire_filename` matches another review’s review template filename (without `.yaml`, case-insensitive).
So sheets mirror **table-generation questions** (and linked follow-up tables), not free-text Q\&A.
**2) Compliance analysis style (`enable_compliance_analysis_export_style`)**
* A **separate** **XLSX** button appears when this review template flag is on.
* **Single worksheet** with one row per **`freeform`**, **`single_select`**, or **`multi_select`** block.
* **Columns:** `Question` | `Answer` | `Compliant` | `Compliance Details` | `Analysis`
* `Answer` / `Analysis`: citations **stripped** from text.
* `Compliant`: `Yes` / `No` from compliance status when set.
* `Compliance Details`: combines additional details and compliance explanation when present.
***
## Configuring a “custom” export [#configuring-a-custom-export]
**Field pickers** (choose columns), **per-format citation toggles**, and **UI-driven “custom export profiles”** are **not** implemented on the export dialog.
**Partial control today (API and workflows only):**
* **`include_confidence`** — When `true`, narrative exports add a `*Confidence:*` line under each answered question when a score exists.
* **`include_explanation`** — When `true`, narrative exports add an `*Explanation:*` line when the model explanation exists. For review templates with **`enable_compliance_analysis_export_style`**, compliance details are always reflected in Markdown-style exports; **non-compliant** answers also force the explanation section in the narrative.
The **in-app Export** buttons do **not** set those flags, so downloads from the UI default both to **off** unless the review template’s compliance rules add explanation text as described above.
***
## Automated exports [#automated-exports]
* **Event-driven automation:** Workflows can use **Attach Review Export to …** (Jira, Azure DevOps, Linear, ServiceNow, etc.) with formats **`markdown`**, **`pdf`**, **`html`**, **`docx`**, or **`csv`** (the same exporter as the UI; **`csv`** may resolve to **XLSX** when `joined_tables_export` is on).
* **API:** Use the Clearly AI API for programmatic access when it is enabled for your organization. Details: [API reference](https://docs.clearly-ai.com/docs/api-reference).
***
## FAQs [#faqs]
Yes, it is on our roadmap!
Your review template may not produce fanout approval data, asset-identification tables, or table-generation rows. Confirm the review actually populated those blocks, or use a narrative format.
This is expected when **`joined_tables_export`** is enabled: the download is a spreadsheet for joined tables.
The review template must set **`special_export: csv`** and/or **`enable_compliance_analysis_export_style`**. Your admin edits YAML (see [Review template schema](https://docs.clearly-ai.com/docs/review-templates/schema)).
Mermaid/Draw\.io rendering can fail during export; failed blocks may fall back to raw diagram text or the original block.
There is not yet a documented JSON schema for full review export from this endpoint. If you need a structured export, use [API access](https://docs.clearly-ai.com/docs/api-reference), use **CSV/XLSX** for tabular flows, or ask your Clearly AI team about **programmatic access** options beyond this doc.
Attachment nodes only allow **`markdown`**, **`pdf`**, **`html`**, **`docx`**, **`csv`** (no separate **`xlsx`** enum in those nodes); use **`csv`** and let joined-table review templates return XLSX when configured.
***
## Related links [#related-links]
| Topic | Link |
| --------------------------------- | ------------------------------------------------------- |
| Workflows | [Workflows](https://docs.clearly-ai.com/docs/workflows) |
| API reference | [API reference](https://docs.clearly-ai.com/docs/api-reference) |
| Review Template flags for exports | [Review template schema](https://docs.clearly-ai.com/docs/review-templates/schema) |
| Jira and tickets | [Jira](https://docs.clearly-ai.com/docs/integrations/issue-trackers/jira) |
| Reviews | [Reviews](https://docs.clearly-ai.com/docs/reviews) |