# Notifications

*Applies to: Patch My PC Publisher*

## Overview

In a multi-tenant configuration, notification behavior differs between email and webhook notifications. It is important to understand how each type is scoped.

## Email Notifications

Only a single email configuration, on the [Alerts tab](https://docs.patchmypc.com/patch-my-pc-publisher/administration/alerts), can be defined for the entire Publisher instance. This configuration applies to all tenants.

If an MSP enables email notifications, the configured email address will receive a single notification after each synchronization cycle. That email will contain publishing details for all tenants processed during that sync.

The email clearly separates activity by tenant so administrators can see which applications or updates were published for each customer.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2F99NexUx3Dm1Xut6joKri%2Fimage.png?alt=media&#x26;token=21cc06d6-86d5-4c82-b1df-38fe3325ed6a" alt="Multi-tenant Email Notifications" width="563"><figcaption></figcaption></figure>

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

Email notifications cannot be configured per tenant. It is not possible to send separate synchronization emails to individual customer email addresses. For this reason, MSPs typically configure a centralized operations or service mailbox to receive synchronization notifications.
{% endhint %}

## Webhook Notifications

Webhook notifications *do* support per-tenant configuration.

When configuring webhook notifications, you can specify which tenant the webhook applies to. This allows you to create separate webhook entries for different tenants configured in the Publisher.

Each webhook can have:

* A different webhook URL
* A different notification level
* Independent scope and event configuration

This enables flexible notification routing. For example:

* Webhook notifications can be sent to the MSP parent company.
* Webhook notifications can be sent directly to individual MSP customers.

Within the webhook configuration window, use the **Tenant Selection** section to control scope. If no tenants are selected, the webhook applies to all tenants. If one or more tenants are selected, the webhook applies only to the selected tenants.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FQRLtREP4U28QYaeFLWOb%2Fimage.png?alt=media&#x26;token=4694da58-d8e8-44d4-9fad-a1d109203cb4" alt="Tenant Specific Webhook Notifications" width="450"><figcaption></figcaption></figure>

This provides granular control over how and where notifications are delivered in a multi-tenant Publisher scneario.

For detailed guidance on how to create and configure a webhook in the Publisher, see [Webhook Notifications](https://docs.patchmypc.com/patch-my-pc-publisher/administration/alerts/webhook-notifications).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.patchmypc.com/patch-my-pc-publisher/administration/intune-apps-updates/multi-tenant/notifications.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.