> 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-xdr-5.x/configure-cortex-xdr/managed-services-configuration.md). # Managed Services configuration Configure Cortex XDR for managed security services. The Managed Services configuration page in Cortex XSIAM and XDR governs how the Unit 42 Managed Services team engages with your environment when the team hunts, investigates and responds to threats on your behalf. The Managed Services page is available to Cortex XSIAM and XDR customers subscribed to Unit 42 Managed Services. The Managed Services page is identifiable by the Unit42 Managed Services banner with a lock icon, displayed at the top of the page. The banner indicates that the settings govern the operations performed by the Unit 42 Managed Services team in your tenant. The Managed Services page contains two tabs: * **General**: Configures the email distribution list for Managed Services reports and the actions permissions matrix, which defines how the Unit 42 Managed Services team operates in your environment. * **Escalation contacts**: Maintains the ordered list of contacts that the Managed Services team contacts during an incident. --- # 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-xdr-5.x/configure-cortex-xdr/managed-services-configuration.md?ask=&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.