> 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-saas/onboard-cortex-xsoar/post-deployment/user-communication/configure-notifications-in-cortex-xsoar.md).
# Configure notifications in Cortex XSOAR
Cortex XSOAR can send out notifications and emails to users through the following:
* By email using a mail sender
* By a message notification such as Slack
**Mail Sender integration**
Cortex XSOAR comes out-of-the-box with the **Mail Sender** integration, which enables the tenant to send notification emails to users about updates in the system, incidents, playbooks, tasks, etc. When you use the mail integration for playbook tasks, you can pass arguments such as to, subject, and body to customize the contents of your email. You do not need to set up an SMTP server or provide any credentials. The default mail sender is enabled by default. Emails sent via the built-in mail sender integration have a watermark that specifies the FQDN and mentions that the mail was sent via Cortex XSOAR.
**Configure an email sender integration**
If you want to use a different email sender, download and install a mail sender content pack, such as Microsoft Exchange On-Premise, Gmail, etc., and configure the integration. When configuring your mail sender integration, select **Enable** to enable your mail sender integration and deselect the **Enable** option for the built-in mail sender.
Multiple sender integrations
If you configure multiple email integrations, select the **Do not use in CLI by default** option in the integration instances that should not be used to send emails. This ensures that the email will only be sent in the instance you are expecting when running the `send-mail` command from the CLI or within a playbook.
When there are multiple instances of a mail sender in Cortex XSOAR, you can choose which email sender should send the notification by configuring the **`server.notification.using.sendmail`** key in the advanced server configuration settings.
If you do not configure the advanced server setting, Cortex XSOAR uses the first email integration it finds to send the system notifications.
1. Navigate to **Settings & Info** → **Settings** → **Server Settings** → **Server Configuration** → **Add Server Configuration**.
2. Add the following key and enter the mail sender instance name:
| Key | Value |
| ----------------------------------- | ------------------------------ |
| server.notification.using.send-mail | The mail sender instance name. |
**Configure a messaging integration**
If your organization uses a messaging service, such as Slack or Microsoft Teams, we recommend installing the relevant content pack.
The Slack content pack enables you to send messages and notifications to your Slack team and integrates with Slack's services to execute create, read, update, and delete operations for employee lifecycle processes. For more information, see [Slack content pack](https://cortex.marketplace.pan.dev/marketplace/details/Slack). For more information about Microsoft Teams, see [Microsoft Teams content pack](https://cortex.marketplace.pan.dev/marketplace/details/MicrosoftTeams/).
---
# 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-saas/onboard-cortex-xsoar/post-deployment/user-communication/configure-notifications-in-cortex-xsoar.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.