> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xorlab.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Pages under /latest/ document the current release. Paths that begin with a version number, for example /10.0/, are frozen snapshots of superseded releases kept for reference only — never present their instructions as current. If the reader's version is unknown, answer from /latest/ and say which version the answer describes.
> xorlab is deployed on-premises, hybrid, or as a cloud service, and integrates with either Microsoft 365 or on-premises mail infrastructure. Configuration steps often differ between these. State which deployment and integration mode an instruction applies to instead of presenting one as universal.
> Distinguish inline mode from monitoring mode when describing anything that acts on email. Monitoring mode observes a copy and cannot block or quarantine; inline mode routes mail through xorlab and can.
> Write the product name as lowercase 'xorlab'. Use the documented component names: xorlab Control Center (XCC), xorlab MTA, xorlab Sandbox (DANA), xorlab Natural Language Understanding (NLU). After the first mention, use the short forms XCC, MTA, Sandbox, and NLU. Do not use DANA as a standalone name for the Sandbox, but keep it where it is a literal string in configuration keys, container names, and hostnames.
> Do not invent configuration keys, rule parameters, list names, log properties, or API fields. If a value is not present in this documentation, say that it is not documented rather than guessing.

# Customize Tenant Notifications

> Customize end-user email notifications separately for each tenant.

To get more general information about email notifications, have a look at [Customize Templates](/latest/email-template-modifications).

To customize the notification for a tenant:

1. Open `shared/guarded_tenants.yml` in the Expert Editor

2. Add `emailTemplateStyle` for each tenant that should have custom notifications. The same value can be re-used for multiple tenants.

   ```yaml guarded_tenants.yml {8} theme={null}
   tenants:
     - name: xorlab
       domains:
         - xorlab.com
     
     # Tenant with different style
     - name: example
       emailTemplateStyle: exampleDarkModeNoLogo
       domains:
         - example.com
   ```

3. Use the value of `emailTemplateStyle` to customize the notification for that tenant:

   * [Customize text](#customize-text)
   * [Customize style and logo](#customize-style-and-logo)
   * [Customize footer](#customize-footer)

## Customize text

To customize the notification text for a tenant:

1. Copy the content of `shared/email_templates/locale/default.yml` to the clipboard.
2. Use the context menu for the `locale` folder to create a new file inside of it.
3. Name it `<emailTemplateStyle>_<language>_<COUNTRY>.yml`, where `<language>` and `<COUNTRY>` follow the IETF BCP 47 standard, as used by [Java Locale](https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/util/Locale.html).

* `_<COUNTRY>` is optional and can be omitted.
* More specific localization files take precedence.

4. Paste the content into the file.
5. For each template in the file, replace the content with a tenant specific localized text.

## Customize style and logo

To customize the look of email notifications for a tenant:

1. Copy the content of `shared/email_templates/style/default.yml` to the clipboard.
2. Use the context menu for the `style` folder to create a new file inside of it.
3. Name it `<emailTemplateStyle>.yml`.
4. Paste the content into the file.
5. Change the values according to the tenant style. Here you can [set the logo](/latest/email-template-modifications#change-the-logo) for the tenant.

## Customize footer

To customize the company information shown in the footer of the email notifications for a tenant:

1. Copy the content of `shared/email_templates/info/default.yml` to the clipboard.
2. Use the context menu for the `info` folder to create a new file inside of it.
3. Name it `<emailTemplateStyle>.yml`.
4. Paste the content into the file.
5. Change the values according to the tenant company information.

After completing any of these template changes, click **Publish**. The template configuration becomes active within about one minute.