> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/managed-services-configuration-in-cortex/configure-report-forwarding.md).

# Configure report forwarding

Configure an email address or distribution list to receive Cortex XSIAM reports from Unit 42 Managed Services.

Configure the email distribution list that receives Managed Services reports from the Unit 42 Managed Services team.

**Prerequisites**

* Access to the Managed Services configuration page.
* An email address or distribution list intended to receive Managed Services reports.

1. Navigate to **Settings** → **Configuration** → **Managed Services**.
2. In the **General** tab, under **Report forwarding**, in the **User email** field, enter the email address or distribution list that receives Managed Services reports.
3. Click **Save** to save the email address to the system.

The Unit 42 Managed Services team sends Managed Services reports to the configured email distribution list.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/managed-services-configuration-in-cortex/configure-report-forwarding.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.