> 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/manage/settings/notifications/create-email-notification.md).

# Create an Email Notification in Patch My PC Cloud

*Applies to: Patch My PC Cloud*

You can create an email notification in Patch My PC (PMPC) Cloud to automatically receive a daily email report with details of all deployments that have been created and updated after the daily sync with our publishing service has been completed.

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

We strongly recommend you create at least one email notification so you can easily track what is happening in your environment. See [Example Updates Report Email](/patch-my-pc-cloud/technical-references/cloud-email-reference/example-cloud-updates-report-email.md) for an example of the Updates Report email you will receive six hours after the daily sync job has run.
{% endhint %}

To create an email notification:

1. Navigate to **Settings | Notifications**
2. On the **Add Notifications** screen, enter a unique name for this notification in the **Name** field.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FHCjwPb9i64z1668Xsfmd%2Fimage.png?alt=media&amp;token=c0afc38e-b9e9-4a54-ae43-fe0624af4b21" alt="&#x27;Add Notifications&#x27; screen" width="563"><figcaption></figcaption></figure>

3. In the **User Email** field, select the relevant administrator’s email address from the dropdown or type their email address.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FWPECP2BkutPit6zzXXiD%2Fimage.png?alt=media&amp;token=199240e4-3ca1-4640-96d3-f2680b5f02cc" alt="Selecting the relevant administrator’s email address from the dropdown or type their email address" width="563"><figcaption></figcaption></figure>

The user's email address is added to the **Email** list that will receive the notification.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FHHOE9CQCgHJWwJhLMTfn%2Fimage.png?alt=media&amp;token=530bc176-4b45-41b7-96ba-90f85859b847" alt="User&#x27;s email address is added to the email list that will receive the notification" width="563"><figcaption></figcaption></figure>

4. Repeat Step 3 to add any additional email addresses.

{% hint style="success" %}
**Tip**

You can click the small envelope beside the email address (![](https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2Fxf8HI9He9w4GO5gATVFh%2Fimage.png?alt=media\&token=7e292d89-fcce-4f5a-8a2c-bc779c834575)) to send a test notification. See [Testing an Email Notification](/patch-my-pc-cloud/manage/settings/notifications/technical-references/test-email-notification.md) for more details.
{% endhint %}

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

You can add more than one email address. The email address must be in a valid format and can be for an address outside your Intune tenant.

You can also click the trashcan beside an email address to delete it from the list of email addresses to be notified (you may need to scroll down to see the full list).
{% endhint %}

5. Click **Save** on the **Add Notifications** screen to save the notification.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FGdyVwThTqO8gy9yvjlwy%2Fimage.png?alt=media&amp;token=1ff1e7be-0ef4-4914-909b-aae4af7b6a0d" alt="Clicking &#x27;Save&#x27;" width="563"><figcaption></figcaption></figure>

The **Success - Notification created** notification is shown.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2Fq93Td6AgHOeID3V2QU1m%2Fimage.png?alt=media&amp;token=0fe21464-7a86-4026-a880-a40f82fa0d3c" alt="&#x27;Success&#x27; notification" width="563"><figcaption></figcaption></figure>

The Cloud Portal auto-refreshes to show the new notification, including abbreviations of the users who will receive the email notification.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FAV3yC8hZBllu7z7ho0wY%2Fimage.png?alt=media&amp;token=93f4a322-ef35-4d56-ad23-eb0dbded5739" alt="Cloud Portal auto-refreshing" width="563"><figcaption></figcaption></figure>


---

# 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/manage/settings/notifications/create-email-notification.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.
