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

# Request Release

The Request Release feature allows end-users to request the release of emails in their Self-Service Quarantine (SSQ). Analysts can then review these requests and decide whether to release or deny them.

**How it works:**

* The feature must be enabled **separately for each quarantine**
* It only applies to quarantines where **end-users do not already have release permissions**
* To enable it, add `canRequestRelease: true` to a quarantine in the `guarded_tenants.yml` file via the Expert Editor

For example, this configuration in `guarded_tenants.yml` enables the feature for the Phishing quarantine.

```yaml hl_lines="8" theme={null}
tenants:
  - uid: 00000000-0000-0000-0000-000000000000
    name: xorlab.com
    quarantine:
      - name: Phishing
        canView: false
        canRelease: false
        canRequestRelease: true    
```

## End-user view

For emails in an eligible quarantine, the end-user sees a Request Release button in the upper-right corner.

* After clicking the button, the email status changes to: `RELEASE REQUESTED`
* Once an analyst reviews the request, the status updates to:

  * `RELEASE APPROVED` – if the analyst releases the email
  * `RELEASE DENIED` – if the analyst denies the request (the email stays in quarantine)

<img src="https://mintcdn.com/xorlab/O_O2TUa6eRBR54aI/9.0/assets/request_release_ssq.png?fit=max&auto=format&n=O_O2TUa6eRBR54aI&q=85&s=2685c7dba1901cd7a04230f38cba93b4" alt="Request Release" width="1415" height="819" data-path="9.0/assets/request_release_ssq.png" />

## Analyst view

Analysts can manage release requests by:

* Filtering emails by the status `RELEASE REQUESTED`
* Opening the detail view of an email to either:

  * Release the email → status changes to `RELEASE APPROVED`
  * Deny the request → status changes to `RELEASE DENIED`

<Tip>
  **Saved Search**

  Create a saved search for the status `RELEASE REQUESTED` to quickly access all pending requests.
</Tip>

<img src="https://mintcdn.com/xorlab/O_O2TUa6eRBR54aI/9.0/assets/request_release_analyst.png?fit=max&auto=format&n=O_O2TUa6eRBR54aI&q=85&s=4e86869144625ba3cc469678152851dd" alt="Request Release" width="537" height="363" data-path="9.0/assets/request_release_analyst.png" />

## Triggering notifications

You can configure notifications to be triggered when specific release request events occur.

* `audit.quarantine.release.request.created` – A user has submitted a release request
* `audit.quarantine.release.request.approved` – An analyst has approved and released the email
* `audit.quarantine.release.request.denied` – An analyst has denied the release request

For details on configuring notifications, see [Logging](/9.0/logging).

You can, for example:

* Send an **email notification** when a release request is created, using an [Email Appender](logging-appenders.md/#email)
* Forward events to your **SIEM** using a [Syslog Appender](logging-appenders.md/#syslog)