> ## 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.

# Assign Reported Emails to Tenants

> Assign reported emails to the correct tenant using the x-ag-tenant header on the carrier email.

1. Add a `x-ag-tenant` email header that contains the tenant name to the outer email of a reported email.

2. xorlab will parse the header and assign the reported email to the correct tenant.

3. Optional: Follow [Tenant-Specific Notifications](/latest/multi-tenancy-email-templates) to customize notifications per tenant.

<Note>
  **Custom email header**

  To read the tenant from a different header, for example, `my-custom-tenant-header` instead of `x-ag-tenant`, you need to edit `activeguard/core/active_guard.yml` the following way:

  ```yaml active_guard.yml theme={null}
  emailReporting:
      ## Header name for tenant identification (default = x-ag-tenant)
      tenantIdentifyingMailHeaderName: my-custom-tenant-header
  ```

  Afterward, click **Publish**, then restart all MTAs. The `emailReporting` setting in `active_guard.yml` requires an MTA restart; see [How to Activate the Configuration](/latest/activate-configuration).

  The tenant value must consist of letters (a-z, A-Z), numbers (0-9), underscores (\_), and hyphens (-). Note: periods (.) are not allowed.
</Note>