> 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/what-would-you-like-to-learn-about/platform-features/multi-program-reports/report-management/manage-reports.md).

# Manage Reports

<a href="https://pxa.impact.com/student/activity/1099652?sid=0c0e3e5c-54c9-4435-9bee-ebcdccb7f292&#x26;sid_i=0?utm_source=app.impact.com&#x26;utm_medium=owned-platform&#x26;utm_content=fund-lp-150&#x26;utm_campaign=help-center" class="button primary">Take the PXA course</a>

When you open a report and change any view settings, you can save that report view or schedule it to be delivered to you. On the *More Reports* screen, you can view all your reports, including saved views and scheduled reports, and you can pin specific reports to your left menu bar.

{% hint style="info" %}
**Note:** Any modifications you make to reports will only be reflected for your user and not all account users.
{% endhint %}

#### Access More Reports

Each report on the *More Reports* screen has a name with a corresponding *Description* of what the report displays.

1. From the left navigation menu, select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage] → Reports →** [More Reports](https://app.impact.com/secure/advertiser/engage/fr/all_reports.ihtml).
2. On the *More Reports* screen, hover over a report to do the following:
   * To add or remove the report from your left navigation menu, select **Pin** or **Unpin**.
   * To modify view settings, select **View** to open the report, adjust the filters according to your preferences, and select **Save** next to the report heading.
   * Learn how to [save](/brand/what-would-you-like-to-learn-about/platform-features/multi-program-reports/report-management/save-reports.md), [schedule](/brand/what-would-you-like-to-learn-about/platform-features/multi-program-reports/report-management/schedule-reports.md), [download](/brand/what-would-you-like-to-learn-about/platform-features/multi-program-reports/report-management/download-a-report.md), and [export](https://integrations.impact.com/brand-api-reference/reference/report-export/report-export) reports via API to always have the latest data for your account and programs.
3. Select **Build Report** in the upper-right corner to create a custom report using [Data Lab](/brand/what-would-you-like-to-learn-about/platform-features/multi-program-reports/data-lab-custom-reports/data-lab-introduction.md).
4. Select **Category** to filter reports by a specific category, e.g., *Performance*, *Finance*, or *Custom* reports.
   * Alternatively, enter a report name in the *search bar* field to find a specific report.


---

# 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/what-would-you-like-to-learn-about/platform-features/multi-program-reports/report-management/manage-reports.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.
