> 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/cortex-xsoar-8-on-prem/8.13/onboard-cortex-xsoar/post-deployment/user-communication/customize-system-emails.md). # Customize system emails Cortex XSOAR sends notifications to users. You can customize the subject and the contents of the email, and choose whether to send the email in HTML format. The following are the default message subjects and the default message contents: | Message Type | Default Subject | Default Message Body | | ---------------------- | ----------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | mentionNew | Message from Cortex XSOAR Security Operations Server | {{`.username`}} added you to investigation {{`.invName`}}.\nYou were mentioned: {{`.parentContent`}}. | | mentionNewNoContent | Message from Cortex XSOAR Security Operations Server | {{ `.username`}} added you to investigation {{ `.invName`}}. | | mentionOld | Message from Cortex XSOAR Security Operations Server | {{ `.username`}} mentioned you in investigation {{ `.invName`}}: {{ `.parentContent`}}. | | assign | Message from Cortex XSOAR Security Operations Server |

{{ .username}} assigned task #{{ .taskId}} in investigation {{ .invName}} to you.

Note

The assign message type is only relevant for Playbook tasks.

| | todoAssign | Message from Cortex XSOAR Security Operations Server | {{`.username`}} assigned To-Do task {{`.title`}} in investigation {{`.invName`}} to you. | | taskCompleted | Message from Cortex XSOAR Security Operations Server | {{ `.username`}} completed task #{{ `.taskId`}} in investigation {{.invName }}. | | taskUpdated | Message from Cortex XSOAR Security Operations Server | {{`.username`}} updated task #{{`.taskId`}} in investigation {{`.invName`}}. | | investigationClosed | Message from Cortex XSOAR Security Operations Server | {{`.username`}} has closed investigation {{`.invName`}}. | | investigationWaiting | Message from Cortex XSOAR Security Operations Server | {{`.username`}}, {{`.invName`}} has stopped and is waiting your instructions." | | investigationError | Message from Cortex XSOAR Security Operations Server | {{`.username`}}, {{`.invName`}} has stopped because of an error. | | investigationDeleted | Message from Cortex XSOAR Security Operations Server | {{`.username`}} has deleted investigation {{`.invName`}}. | | incidentOpened | Message from Cortex XSOAR Security Operations Server | {{`.username`}} has reported {{`.incTermArticle`}} {{`.incTermSingular`}} {{`.invName`}}. | | incidentChanged | Message from Cortex XSOAR Security Operations Server | {{`.username`}} has updated {{`.incTermArticle`}} {{`.incTermSingular`}} {{`.invName`}}. | | incidentStatusChanged | Playbook has stopped on {{ `.runStatus`}} for {{ `.invName`}} (#{{ `.incID`}}) | {{`.incTermCapitalSingular`}} playbook task "{{`.taskName`}}" stopped on {{`.runStatus`}}. {{`.incTermCapitalSingular`}} Id: #{{`.incID`}}{{`.incTermCapitalSingular`}} Name: {{`.invName`}}{{`.incTermCapitalSingular`}} SLA: {{`.SLA`}}{{`.incTermCapitalSingular`}} Severity: {{`.severity`}}Task: #{{`.taskID`}}Task Name: {{`.taskName`}}Task SLA: {{`.TaskSLA`}} | | incidentAssigned | Message from Cortex XSOAR Security Operations Server | {{`.username`}} has assigned you {{`.incTermArticle`}} {{`.incTermSingular`}} {{`.invName`}}. | | taskCompletedWithNotes | Message from Cortex XSOAR Security Operations Server | {{`.username`}} completed task #{{`.taskId`}} in investigation {{`.invName`}}.\nCompletion note was: {{`.taskComment`}} | | incidentReminderSLA | Message from Cortex XSOAR Security Operations Server | FYI, {{`.incTermSingular`}} #{{`.invID`}} "{{`.reminedOn`}}" - SLA expiration is approaching. ({{`.SLA`}}) | | MessageTypeTaskSLA | Message from Cortex XSOAR Security Operations Server | FYI, task "{{`.reminedOn`}}" (from investigation {{`.invName`}}) - due date is approaching. ({{`.SLA`}}) | | newContentAvailable | Message from Cortex XSOAR Security Operations Server | A content update: {{`.release`}} for your Demisto Server is available.\n{{`.releaseNotes`}} | | failedFetchIncidents | Integration instance {{ `.instance`}} ({{ `.brand`}}) failed fetching new {{ `.incTermPlural`}} | Integration instance {{`.instance`}} ({{`.brand`}}) failed fetching new {{`.incTermPlural`}} at {{`.date`}}\nerror message is:\n{{`.error`}} | | engineDisconnected | Cortex XSOAR Engine Disconnected | Engine '{{`.name`}}' ({{`.host`}}) is disconnected. Engines will not process integration automations until it is reconnected. | | externalFormSubmit | {{ `.subject`}} | "" | | externalAskSubmit | {{ `.subject`}} | "" | | jobRunning | Message from Cortex XSOAR Security Operations Server | A previous instance of job {{`.invName`}} is already running. | **Change the email subject** You can customize the subjects of system emails. 1. Go to **Settings & Info** → **Settings** → **System** → **Server Settings** → **Server Configuration**. 2. Add the key **`messages.subject.formats.`**, where **``** is the type of message, such as **`assign`** or **`taskCompleted`**. For the value, enter your custom subject. You can use any of the default variables, for example `.invName` in your subject. Examples: | Key | Value | | -------------------------------------------- | -------------------------------- | | **`messages.subject.formats.assign`** | You were assigned to an incident | | **`messages.subject.formats.taskcompleted`** | Task completed in {{.invName }} | **Change the email body** You can customize the content of the system messages, and include variables such as `.username` and `.invName` in your body content. You can send HTML or non HTML messages. If you have users who can only receive plain text, use the key **`messages.formats.`**, where **``** is the type of message, such as **`assign`** or **`taskCompleted`**. Enter your custom body text as the value. If you have users who can receive HTML emails, use the key **`messages.HTML.formats.`**, where **``** is the type of message. Enter your custom body text as the value. To set custom body text for both text and HTML messages, add both keys/values for each message you want to customize. 1. Go to **Settings & Info** → **Settings** → **System** → **Server Settings** → **Server Configuration**. 2. Add the key **`messages.formats.`** or **`messages.HTML.formats.`**. For the value, enter your custom email body. Examples: | Key | Value | | ---------------------------------- | ------------------------------------------------------------------------------------- | | **`messages.HTML.formats.assign`** | {{`.username`}} added you to investigation {{`.invName`}}.\nPlease log in and review. | | **`messages.formats.assign`** | {{`.username`}} added you to investigation {{`.invName`}}.\nPlease log in and review. | --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.13/onboard-cortex-xsoar/post-deployment/user-communication/customize-system-emails.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.