> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-cloud/managed-service-provider-feature/managed-service-provider-administration/manage-msp-events.md).

# Manage MSP Events

*Applies to: Patch My PC Cloud*

The **Events** node of the parent Managed Service Provider (MSP) Patch My PC (PMPC) Cloud company only shows events that occurred in the parent company or events performed in the parent company that affect the child company. For example:

* The creation of a child company, which shows as a regular company being created on the child company, but on the parent company the following event is created:\
  \
  **"Managed company <*****company\_name>*****&#x20;was created."**
* The removal of the relationship between the parent company and a child company, which appears the same on both the parent and child company.

The **Events** node of the child company shows all of the events performed by both the parent company administrator on the child company and any events performed on the child company by the administrator users of that company.

{% hint style="info" %}
**Note**

Events that occur on any child companies are not replicated up to the parent company.
{% 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://docs.patchmypc.com/patch-my-pc-cloud/managed-service-provider-feature/managed-service-provider-administration/manage-msp-events.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.