> ## Documentation Index
> Fetch the complete documentation index at: https://support.duna.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data export

> [!TIP]
>
>   **Admins**, **Reviewers**, **Task Reviewers** and **Members** can use this feature. See [Roles](https://support.duna.com/roles.md#connections).

To hand to an auditor or regulator a clear export of the due diligence performed on a [Connection](https://support.duna.com/connections.md), you can download Due Diligence Files.

## Content

The export is one ZIP file with five PDF reports. Each one answers a different question:

| Report | Answers | Contains |
| :- | :- | :- |
| **Connection** | How does this relationship fit together, and how has it changed over time? | A summary of the business and the people behind it, a short summary of each Onboarding and [Review](https://support.duna.com/managing-reviews.md), and a timeline of the relationship with changes in risk over time. |
| **Onboarding** | What information did the business supply, and what did you collect about them? | Everything collected during each Onboarding, grouped by business and person: details entered by the business, registry data, identity verification results and uploaded documents. A timeline of when the Onboarding started, was submitted, returned, completed, canceled or expired. |
| **Review** | What did your analysts decide, and why? | The decision for each Capability, [Sign-offs](https://support.duna.com/sign-offs.md), risk assessments, task assessments, Review and task notes, [Follow-ups](https://support.duna.com/follow-ups.md) and their history, and a timeline of the [Review](https://support.duna.com/managing-reviews.md)’s key steps. |
| **Screening** | Who was screened, when, and against which lists? | Every screening run per person and business, the lists and settings used, and the monitoring history showing that screening continued over time. |
| **Investigations** | How did your analysts handle the screening and monitoring hits? | Each investigated hit grouped by outcome, with true positives first. For each one: the analyst’s assessment, their reasoning and the resolution. Unresolved hits stay visible. |

## Generate and download

1. Open the [Connection](https://support.duna.com/connections.md), or find it in the **Connections** list and open the ••• menu.
2. Click **Generate Due Diligence Files**.
3. Once they’re ready, click **Download Due Diligence Files**. Generating can take a few minutes.

Your developers can request, poll and download the files via the `due_diligence_files` endpoints.

> [!NOTE]
>
> Files stay available for **7 days** after they’re generated.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.