> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/incidents/export.md).

# Export your data breaches

Export the record of incidents, a selection of incidents or a single incident, as PDF, Word, HTML, Excel, CSV, JSON or Markdown.

You can export the whole record of incidents, a selection of incidents or a single incident, for example to answer a request from the supervisory authority or to archive a closed incident.

## Export the record

1. Open **Operations** > **Incidents** > **Record of incidents**. Apply filters if you only want to export part of the record: the export uses the active filters.
2. Click the arrow on the right of the **Create an incident** button, then **Export**.

   <figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-79fe75b1e17eb0915bc052e176efd77a6be46024%2Fincidents-export-1.png?alt=media" alt="Create an incident button menu with the Import, Export, Share and Read the documentation entries"><figcaption><p>The menu of the Create an incident button, with the Export entry</p></figcaption></figure>
3. In the window that opens, under **Choose an export format**, select PDF, Word, HTML, Excel, CSV, JSON or Markdown.
4. Click **Download file**.

   <figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-f882b12b82dea99b9e297783e0fb89077ebb1666%2Fincidents-export-2.png?alt=media" alt="Export window with the list of formats and the Download file button"><figcaption><p>The export window</p></figcaption></figure>

The **Export** entry is greyed out when the record is empty or when your role does not allow exporting.

## Options by format

* **Include table of contents** for the PDF, Word, HTML and Markdown formats.
* **Use native column names or reports (recommended for importing data)** and **Export custom fields** for the CSV and Excel formats. Native column names let you import the file again: see [Import your data (Excel, Csv)](https://doc.dastra.eu/en/features/general/import.md).

PDF, Word and HTML exports include up to 500 incidents, and CSV, Excel, JSON and Markdown exports up to 10,000. If your selection is larger, the window warns you that only the first items are exported.

## Export a selection or a single incident

* In the record, tick the rows you want, then click **Export** in the action bar of the selection.
* In the form of an incident, open the arrow of the **Save changes** button, then click **Export**.

The export window is the same.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.dastra.eu/en/features/incidents/export.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
