> 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-publisher/manage/alerts-tab/overview.md).

# Overview of Alerts in Patch My PC Publisher

*Applies to: Patch My PC Publisher V3.x*

The **Alerts** tab in Patch My PC (PMPC) Publisher provides visibility into publishing activity and operational events. Alerts are generated during [publishing syncs](https://docs.patchmypc.com/patch-my-pc-publisher/manage/sync-tab/overview.md) to inform administrators about successful actions, warnings, and failures.

*Alerts* are intended to help administrators quickly understand the state of the publishing process without needing to review detailed logs.

Publisher supports both email and webhook notification delivery methods. They can notify when apps and updates are published successfully, when updates are skipped due to configuration, or when errors occur that require attention.

Clicking the **Alerts** tab by default takes you to the [Email Alerts](https://docs.patchmypc.com/patch-my-pc-publisher/manage/alerts-tab/email-alerts-tab.md) tab.


---

# 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-publisher/manage/alerts-tab/overview.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.
