> 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/pin-a-report.md).

# Épingler un rapport

Vous pouvez épingler n’importe quel rapport que vous trouvez sur l’ **Plus de rapports** écran au menu de navigation de gauche. Les rapports épinglés apparaîtront dans un menu déroulant étiqueté selon le type de rapport. Par exemple, un rapport épinglé *Performance* apparaîtra dans le *Performance* menu déroulant. La plupart des menus déroulants (par ex., *Opérations*) n’apparaîtront pas dans le menu de navigation de gauche avant que vous n’ayez épinglé un rapport de ce type.

1. Dans le menu 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 → Plus de rapports**.
2. Trouvez le rapport que vous souhaitez épingler à votre menu de navigation de gauche.
   * Utilisez les filtres en haut de l’écran pour faciliter votre recherche.
3. Survolez le rapport avec votre curseur et sélectionnez ![](https://57104473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FKG07S1laT6SIusRgHwBA%2FPin.svg?alt=media\&token=1fef79ba-7abe-4eb4-8341-5b33074bee1c) **\[Épingler]** pour épingler le rapport.


---

# 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/pin-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.