> For the complete documentation index, see [llms.txt](https://docs.monolithforensics.com/monolith/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.monolithforensics.com/monolith/relay-request-portal/relay-overview.md).

# Relay Overview

Relay is Monolith's request portal for collecting structured forensic requests from people outside of your primary Monolith user base.

Instead of receiving requests through email, phone calls, spreadsheets, web forms, ticketing systems, or other disconnected channels, Relay gives requestors a consistent place to submit the information your team needs before forensic work begins.

Requests submitted through Relay flow directly into [**Case Management > Inquiries**](/monolith/relay-request-portal/relay-overview/managing-relay-requests-in-monolith.md) in Monolith, where your team can review the submitted information, update the inquiry status, and ultimately create a new case or merge the inquiry into an existing case.

Request-specific messaging remains in Relay. Monolith users who need to communicate with requestors through Relay should also have an appropriate Relay account.

### Why Use Relay?

Forensic teams often receive requests from many more people than the small group of users performing the actual forensic work.

A Monolith environment may have only a handful of licensed Monolith users while supporting hundreds of requestors through Relay.

Relay helps your team:

* Standardize how forensic requests are submitted
* Collect important case and evidence information before intake
* Reduce back-and-forth communication caused by incomplete requests
* Keep request information connected to the resulting Monolith case
* Give requestors visibility into request and case progress
* Provide request-specific communication through Relay comments and @mentions
* Share files securely through [Case Drives](/monolith/relay-request-portal/relay-overview/using-relay.md#case-drives)
* Avoid maintaining a separate intake form, ticketing system, or request website
* Support large populations of requestors without requiring each person to have a Monolith license

Relay users do not consume Monolith user licenses, and an organization can support as many Relay users as needed.

### How Relay Fits Into Monolith

A typical Relay workflow looks like this:

```
Requestor
    ↓
Submit Request in Relay
    ↓
Inquiry Created in Monolith
    ↓
Review and Triage in Monolith
    ↓
Update Inquiry Status
    ↓
Communicate in Relay, if needed
    ↓
Physical Evidence or Required Information Received
    ↓
Create New Case
       or
Merge Into Existing Case
    ↓
Normal Monolith Casework
    ↓
Case and Evidence Progress Visible in Relay
```

{% hint style="info" %}
Relay and Monolith are separate applications. Inquiry review, status management, and case conversion occur in Monolith, while request-specific comments and @mentions are handled within Relay. Monolith users who need to participate in Relay messaging should also have a Relay account with the appropriate permissions.
{% endhint %}

### Next Steps

Choose the guide that best matches how you use Relay:

* [**Using Relay** ](/monolith/relay-request-portal/relay-overview/using-relay.md)- Learn how to submit requests, add evidence and contacts, track progress, communicate with the forensic team, and access shared files.
* [**Managing Relay Requests in Monolith**](/monolith/relay-request-portal/relay-overview/managing-relay-requests-in-monolith.md)  - Learn how forensic teams review incoming Inquiries, manage request status, and create or merge cases.
* [**Relay Administration** ](/monolith/relay-request-portal/relay-overview/relay-administration.md)- Configure your Relay tenant, manage user access, provide request instructions, and control custom fields.