> 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.12/reference-docs/reference/server-configurations/notification-server-configurations.md). # Notification Server Configurations Reference notification server configurations in Cortex XSOAR 6.12. | Key | Description | Default | | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- | | **`content.notification.enabled`** | Set to true to enable notification for new content updates. | **`false`** | | **`content.notification.users`** | Notifies all users by email when there is a content update available (comma separated user names in Cortex XSOAR). | N/a | | **`message.ignore.failedFetchIncidents`** | Whether to ignore failed fetch incident messages. For more information, see [Receive Notification on an Incident Fetch Error](/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/incidents/incident-lifecycle.md#UUID-12fb615d-80cd-07a1-adf5-18c58ce2e174). | **`false`** | | **`message.ignore.incidentChanged`** | Whether to disable notifications when an incident is changed. | **`false`** | | **`message.ignore.incidentStatusChanged`** | Whether to disable notifications when an incident status is changed. | **`false`** | | **`message.ignore.incidentOpened`** | Whether to disable notifications, when an incident is opened. | **`false`** | | **`message.ignore.incidentAssigned`** | Whether to disable notifications when an incident is assigned. | **`false`** | | **`message.ignore.investigationClosed`** | Whether to disable notifications when an incident is closed. | **`false`** | | **`message.ignore.assign`** | Whether to disable notifications when a to do task is assigned to you. | **`false`** | | **`message.ignore.mentionNew`** | Whether to disable notifications when a user is mentioned (@username), if the user is not already part of the incident. | **`false`** | | **`message.ignore.mentionOld`** | Whether to disable notifications when a user is mentioned (@username), if the user is already part of the incident. | **`false`** | | **`Messages.Formats.MessageType`** | Changes the email body when using plain text. For more information, see [Change the Email Subject](/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/system-settings/customize-system-emails.md#UUID-e79c43f8-9cf7-2d8c-fe2a-349512bea2c7_id0f9a0a77-1377-4f7a-afca-ccc427a77052). | N/a | | **`Messages.HTML.Formats.MessageType`** | Changes the email body when using HTML. For more information, see [Change the Email Subject](/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/system-settings/customize-system-emails.md#UUID-e79c43f8-9cf7-2d8c-fe2a-349512bea2c7_id0f9a0a77-1377-4f7a-afca-ccc427a77052). | N/a | | **`Messages.Subject.Formats.assign`** | Changes the subject of an email when assigned an incident in the format, **`{{.username}} added you to investigation {{.invName}}.\nPlease log in and review`**. For more information, see [Change the Email Subject](/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/system-settings/customize-system-emails.md#UUID-e79c43f8-9cf7-2d8c-fe2a-349512bea2c7_id0f9a0a77-1377-4f7a-afca-ccc427a77052). | N/a | | **`Messages.Subject.Formats.TaskCompleted`** | Changes the subject of an email when a task is completed. For more information, see [Change the Email Subject](/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/system-settings/customize-system-emails.md#UUID-e79c43f8-9cf7-2d8c-fe2a-349512bea2c7_id0f9a0a77-1377-4f7a-afca-ccc427a77052). | N/a | | **`module.health.notification.time.format`** | The date format for the notifications sent when the percentage of indicators fetched limit is reached, as defined in **`create.indicators.limit.by.total.amount.warning.percentage`** server configuration. | The default format is: (UnixDate = **`Mon Jan _2 15:04:05 MST 2022`**) | | **`module.health.notification.users`** | List of names in CSV format. For example, **`user1,user2,user3`**. For more information, see [Receive Notification on an Incident Fetch Error](/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/incidents/incident-lifecycle.md#UUID-12fb615d-80cd-07a1-adf5-18c58ce2e174). | N/a | | **`server.notification.using.send-mail`** | Select which email sender should send the notification. For more information, see [Configure System Notifications](/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/system-settings/configure-system-notifications.md). | N/a | --- # 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.12/reference-docs/reference/server-configurations/notification-server-configurations.md?ask=&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.