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

# SSQ Overview

> Let end users view and release their own quarantined emails through the Self-Service Quarantine.

The Self-Service Quarantine (SSQ) gives each user access only to their own emails.

For a basic setup follow:

<Card title="Set Up the SSQ" icon="rocket-launch" horizontal href="/latest/ssq-setup" />

Afterward you can further customize it as shown below.

| Step                                                        | Description                                                                                                                            |
| :---------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------- |
| [Set Up the SSQ](/latest/ssq-setup)                         | **Mandatory**. Basic configuration of the SSQ.                                                                                         |
| [Enable Release Requests](/latest/ssq-request-release)      | **Optional**. Allow your users to request the release of dangerous emails in the SSQ.                                                  |
| [Enable Attachment Airlock](/latest/ssq-attachment-airlock) | **Optional**. Quarantine all encrypted attachments that cannot be decrypted. The user can enter the password in the SSQ to release it. |
| [Support Shared Mailboxes](/latest/ssq-shared-mailboxes)    | **Optional**. Allow users to access shared mailboxes in the SSQ.                                                                       |

## Multi-Tenancy

All SSQ configuration lives in `guarded_tenants.yml` and is therefore already tenant-aware. Follow the same steps as above, once per tenant.

There is one exception: for [Support Shared Mailboxes](/latest/ssq-shared-mailboxes), use [Auto-Login](/latest/authentication-auto-login-link). The M365 shared mailbox script is not recommended in a multi-tenant deployment.

You can also give each tenant its own logo and texts in the quarantine notifications, see [Customize Tenant Notifications](/latest/multi-tenancy-email-templates).