> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/outgoing-email.md).

# Outgoing Email

### Introduction

Completing the details on this tab allows a site to send email notifications of events/alarms to various cardholders/operators.

When emails are generated from Configuration Client, they need to pass through this email account to be sent to the recipient. From the recipient’s perspective, it will appear that the email has been sent from this outgoing email address.

**Note:** This tab is only visible if your site is licensed for the Notifications feature.

### Procedure

1. Open the **Command Centre Server Properties** window. [How?](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/opening-the-server-properties-window.md)
2. Click the **Outgoing Email** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-46e813ecb2465746ce67a2992c2386249902a071%2Foutgoingemailtab.png?alt=media)
3. Check the **Enable Outgoing Email Notifications** checkbox.

   All other fields on this screen become enabled.
4. Authentication with your email server can be achieved with Exchange Online authentication or Other (basic) authentication.

   **Note:** Exchange Online email cannot use ‘Other’ authentication as of September 2025 (see ["Deprecation of Basic authentication in Exchange Online"](https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online#impact-to-messaging-protocols-and-existing-applications) on Microsoft Learn).

   To configure via **Exchange Online**, go to Step 5.

   To configure via **Other**, go to Step 6.
5. Configure the **Exchange Online** authentication fields as indicated:

   <table><thead><tr><th width="153">Field</th><th>Description</th></tr></thead><tbody><tr><td>Tenant ID</td><td>Paste the Tenant ID of an Entra ID tenant. This can be found in Entra ID under Properties.</td></tr><tr><td>Client ID</td><td><p>Paste the Client ID of your Entra ID application. To register an Entra ID application, refer to the topic <a href="https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app?tabs=certficate">"Quickstart: Register an application with the Microsoft identity platform"</a> on Microsoft Learn.<br>The application’s Client ID can be found in Entra ID under <strong>App registrations</strong> > <strong>All applications</strong> > <strong>[name of your application]</strong> > <strong>Overview</strong>.<br>The Application must have the following permissions:</p><ul><li>Mail.Send for the Microsoft Graph API</li><li>SMTP.SendAsApp for the Office 365 Exchange Online API</li></ul><p>Refer to <a href="https://learn.microsoft.com/en-us/entra/identity-platform/howto-update-permissions?pivots=portal">"Update an app's requested permissions in Microsoft Entra ID"</a> on Microsoft Learn.</p></td></tr><tr><td>Client Secret</td><td>Paste one of your Entra ID application's client secrets. You can only view a client secret immediately after it is created. If you saved a client secret elsewhere, you can enter it here.<br>Otherwise, create a new one in Entra ID. Refer to the topic <a href="https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app?tabs=certficate">"Quickstart: Register an application with the Microsoft identity platform"</a> on Microsoft Learn, and see the "Add a client secret" section.</td></tr></tbody></table>
6. Configure the **Other** authentication fields as indicated:

   <table><thead><tr><th width="156">Field</th><th>Description</th></tr></thead><tbody><tr><td>Account</td><td>An outgoing email account (username@domain).<br><br><strong>Note:</strong> If an Account is required, but the username/password are incorrect, the user will get an alarm. If no Account is required, but the username/password is provided (even if incorrect), emails will still send without an alarm being generated.</td></tr><tr><td>Password</td><td>A password is only needed if SSL is required.<br><br><strong>Note:</strong> If SSL is required, check the Use SSL checkbox also.</td></tr><tr><td>Server</td><td>The email server DNS name or IP address.</td></tr><tr><td>Port</td><td>The port number.</td></tr><tr><td>Vaidate Server Certificate</td><td>Check the <strong>Validate Server Certificate</strong> checkbox to allow Command Centre to verify the certificate provided to encrypt emails.<br><br><strong>Note:</strong> The <strong>Use SSL</strong> checkbox must be checked to enable this step.</td></tr></tbody></table>

   **Note:** If your site wishes to connect to an SMTP server not supporting authentication, the **Account** and **Password** fields should be left blank.
7. Enter an email address in the **Sender Address** field if required.

   This address will appear as the 'From' address in the email notifications.

   **Note:** If you have selected **Exchange Online**, the **Sender Address** field is required. Do the following with the email address you enter here:

   * In Microsoft 356 Admin Centre, enable **Authenticated SMTP** for the Microsoft account who owns this email address, under **Active users** > **\[user]** > **Mail** > **Manage email apps**.
   * Register the Entra ID application’s service principal in Exchange. Use this email address when giving the service principal access to a mailbox. Refer to the ["Register service principals in Exchange"](https://learn.microsoft.com/en-us/exchange/client-developer/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth#register-service-principals-in-exchange) section on Microsoft Learn.

   **Note:** If you have selected **Other**, and the **Sender Address** field is left blank, what appears as the 'From' address (in the email notifications) is determined as follows:

   <table><thead><tr><th width="305">If 'Incoming Email' is...</th><th>then the...</th></tr></thead><tbody><tr><td>set up,</td><td>'Incoming Email' <strong>Account</strong> will be used to populate the 'From' address.</td></tr><tr><td>NOT set up, and the 'Account' is NOT blank,</td><td><strong>Account</strong> will appear as the 'From' address (including '@&#x3C;servername>' if the <strong>Account</strong> does not include an '@' character).</td></tr><tr><td>NOT set up, and the 'Account' is blank,</td><td>address of 'security@&#x3C;servername>' will appear as the 'From' address.</td></tr></tbody></table>
8. Cardholder-related Email Notifications can optionally contain Personal Data Field details.

   Drag and drop any Personal Data Fields that you want to be included with the event/alarm email notifications (if the Personal Data Field is populated for the cardholder), into the grid.
9. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.


---

# 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://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/outgoing-email.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.
