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

# Using Tenant Config Templates

> Define reusable tenant configuration templates with configSets in guarded_tenants.yml.

A config set supports the following parameters. All those parameters can also be set directly on a tenant.

```yaml guarded_tenants.yml theme={null}
configSets:
  default:
    interTenantMessageSplitting: true
    tenantSelector: {}
    tenantSelectors: []
    autoLoginLink: {}
    quarantine: {}
    dataRetention: {}
    emailTemplateStyle: default
    messageProcessing: {}
    emailReporting: {}
    trustedMTAs: {}
    ruleProfiles: {}

```

Checkout the [guarded\_tenants.yml](/latest/guarded_tenants_yml) for more details what each attribute supports.

<Note>
  You can overwrite single parameters of the `default` set without having to specify all other parameters.
</Note>

You can create new config sets and reference them in some tenants. The `default` set is always applied to all tenants with the least precedence.

```yaml guarded_tenants.yml theme={null}
configSets:
  allowPhishingRequest:
    quarantine:
      quarantines:
          - name: Phishing
            canRelease: true

tenants:
    name: xorlab
    ## Applied config sets, notice that later occurrences will override earlier config set occurrences.
    ## Further, the "default" set is implicitly referenced with least precedence.
    configSets:
        - allowPhishingRequest

```