> 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/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/marketplace/content-pack-update-notifications/customize-content-pack-notifications.md).

# Customize Content Pack Notifications

Customize Cortex XSOAR 6.14 content pack update notifications.

You can customize the time and frequency of content pack update notifications, as well as the length of the release notes for email notifications.

**Change the Frequency and Notification Times**

By default, notifications are sent once a day at 9:00 AM, and only if there is an update to a content pack. You can change the default time for the notification or receive notifications more than once a day.

{% hint style="info" %}

### Note

You cannot set notifications for less than once a day.
{% endhint %}

1. Go to Settings → About → **Troubleshooting**.
2. Add the following server configuration.

   | Key                                              | Value                                                                                                                                                 |
   | ------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
   | **`content.pack.notification.hours.of.the.day`** | A comma-separated list of numbers representing the hours of the day from 0 to 23. For example, **`5,17`** sends notifications at 5:00 AM and 5:00 PM. |

**Change the Length of Included Release Notes**

By default, email notifications include up the first 7 lines of the release note for each content pack. You can customize the length of included release notes.

{% hint style="info" %}

### Note

Non-email notifications, such as to Slack and Microsoft Teams, include content pack names and version numbers, but do not include release notes.
{% endhint %}

1. Go to Settings → About → **Troubleshooting**.
2. Add the following server configuration.

   | Key                                 | Value                                                 |
   | ----------------------------------- | ----------------------------------------------------- |
   | **`email.releasenotes.max.length`** | The number of lines to include for each content pack. |


---

# 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/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/marketplace/content-pack-update-notifications/customize-content-pack-notifications.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.