> 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.14/onboard-cortex-xsoar/post-deployment/user-communication/configure-user-notifications-in-cortex-xsoar.md).
# Configure user 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 integrations**
A mail integration enables Cortex XSOAR to send emails and can be used for system notifications and playbooks. For example, when adding users to Cortex XSOAR, an email invitation is sent to users to log in. When you use the mail integration for playbook tasks, you can pass arguments such as **to**, **subject**, **body**, etc. to customize the contents of your email.
1. Go to **Marketplace**.
2. Search for and download a mail sender content pack (such as Microsoft Exchange On-Premise).
3. Go to **Settings & Info** → **Integrations** → **Instances**.
4. Locate the mail sender integration (for example, EWS v2) and click **Add Instance**.
5. Configure your mail sender integration and select **Enable** to enable your mail sender integration.
6. 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.
Multiple sender integrations
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-on-prem/8.14/onboard-cortex-xsoar/post-deployment/user-communication/configure-user-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.