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

# Review Default Actions

> Decide which verdicts are quarantined and which are delivered with a rewritten subject, and set that per tenant.

The **Actions** configuration screen defines what xorlab does with an email once it has been classified: deliver it, rewrite its subject, or quarantine it. Actions are chosen from the email's verdict and confidence — see [List of Verdicts](/latest/verdicts) for how the final verdict is resolved, and [Understanding an Email Verdict](/latest/understand-verdict) for how a message gets one.

## Review the default actions

Review the default protection settings of xorlab:

1. Open **Admin → Actions** in XCC. Review the configured actions per confidence and verdict.

   1. For a more aggressive detection, set the **Medium Confidence** of the verdicts to quarantine.
   2. Change the default **Subject Rewrite** of *\[SPAM]* if required.
   3. Setting **Low Confidence** to quarantine is not recommended as it will create false positives.

   <img src="https://mintcdn.com/xorlab/O_O2TUa6eRBR54aI/latest/assets/default-actions.png?fit=max&auto=format&n=O_O2TUa6eRBR54aI&q=85&s=f3645d95de7f92536f3838041b434899" alt="Default actions" width="2506" height="1090" data-path="latest/assets/default-actions.png" />

2. In addition to the configured **Actions**, xorlab can quarantine an email due to a static policy. Go through [Review Static Policies](/latest/detection-static-policies).

For changes this screen cannot express, see [Tune Detection](/latest/detection-tuning) and [Rule Parameters](/latest/rule-parameters).

## Multi-Tenancy

Actions are configured per tenant. Select the tenant in the dropdown, then review its **Actions**. To give a tenant a different detection strength altogether, reference a different [rule profile](/latest/rule-profiles) for it.