> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/fr/what-would-you-like-to-learn-about/platform-features/multi-program-reports/report-management/download-a-report.md).

# Télécharger un rapport

<a href="https://pxa.impact.com/student/activity/1117602?sid=0c0e3e5c-54c9-4435-9bee-ebcdccb7f292&#x26;sid_i=0?utm_source=app.impact.com&#x26;utm_medium=owned-platform&#x26;utm_content=opt-350&#x26;utm_campaign=help-center" class="button primary">Suivez la formation PXA</a>

Vous pouvez partager les rapports générés par impact.com avec d’autres parties prenantes, sans qu’elles aient besoin de se connecter elles-mêmes à la plateforme impact.com. Pour ce faire, vous devrez télécharger les rapports depuis impact.com au format CSV, Excel ou PDF. Le rapport sera toujours téléchargé sous forme de tableau, et certains incluront également un graphique.

#### Télécharger un rapport

1. Dans la barre de navigation de gauche, sélectionnez ![](https://57104473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage] → Rapports**, puis sélectionnez le rapport que vous souhaitez exporter.
   * En savoir plus sur [gestion des rapports](/brand/fr/what-would-you-like-to-learn-about/platform-features/multi-program-reports/report-management/manage-reports.md).
2. Dans le coin supérieur droit, sélectionnez ![](https://57104473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-1c990ed7d1179d6bc54ec8a2f98688d63ffdf977%2F1ca7fd10d94ed494c076e86be8f0d3f371693b11c47f1b26ec0435a27e0e48c5.svg?alt=media) **\[Télécharger]**.
3. Dans le menu déroulant, sélectionnez le type de fichier souhaité pour le rapport.

   <div data-with-frame="true"><figure><img src="https://57104473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FIBMMG587Zgcgfy0a2QhB%2FScreenshot%202026-04-27%20at%2016.40.00.png?alt=media&amp;token=2669f796-3b0e-4180-b3a8-882bc55ee688" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}
**Remarque :** La fin des très grands ensembles de données peut ne pas être incluse dans votre fichier téléchargé.
{% endhint %}


---

# 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://help.impact.com/brand/fr/what-would-you-like-to-learn-about/platform-features/multi-program-reports/report-management/download-a-report.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.
