> 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/relay-administration.md).

# Relay Administration

Configure your Relay tenant, manage requestor access, provide intake instructions, and control which custom fields appear in Relay.

Relay administrators configure the request portal from within Monolith under **Settings > Relay Settings**.

These settings control how requestors access your Relay tenant, how the portal is presented, who is allowed to submit requests, what guidance users see before submitting, and which supported custom fields are included in the request workflow.

### Access Relay Settings

In Monolith, navigate to:

**Settings > Relay Settings**

Relay configuration is divided into four areas:

* **Basic Details**
* **User Management**
* **Instructions**
* **Custom Field Options**

Each area controls a different part of the Relay experience.

### Basic Details

Use **Basic Details** to configure the identity and access information for your Relay tenant.

Available settings include:

* **Tenant Logo** — The logo displayed to requestors in Relay.
* **Tenant Name** — The name of your organization as it appears in Relay.
* **Relay URL Slug** — The unique identifier used to create your organization's Relay URL.
* **Tenant Email** — The default email address for the Relay tenant. Relay notifications, such as new users and requests, are sent to this address.

Your Relay URL provides the requestor-facing entry point to your organization's portal. The URL can be distributed to investigators, employees, attorneys, partner organizations, or other people who need to submit work to your team.

The **Relay URL Slug** determines the unique portion of that address. Choose a recognizable identifier that is appropriate for long-term use.

{% hint style="info" %}
Users who register through your Relay URL do not automatically receive access to the tenant. Their access must still be approved through **User Management**.
{% endhint %}

<figure><img src="https://2683670198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCD1iskOdIm8E2TpCd9iZ%2Fuploads%2Fw0DjeTh7GDNnOP79L3uG%2Fbasic-details.png?alt=media&amp;token=dc2c7a04-cbb0-4f70-b763-b64a3cf6c96b" alt=""><figcaption></figcaption></figure>

### User Management

Use **User Management** to control who can access your Relay tenant.

Administrators can:

* Invite users directly
* Review users who registered through your tenant URL
* Approve or deny access
* Manage existing Relay users
* Assign appropriate Relay permissions
* Assign Relay Admin access to Monolith users who also need to review or communicate through Relay

Relay users do not consume Monolith licenses, allowing organizations to support a much larger population of requestors than their licensed Monolith user base.

A Relay account may also have access to multiple Relay tenants when different forensic organizations have granted that user access.

See [**User Management**](/monolith/relay-request-portal/relay-overview/relay-administration/user-management.md) for more information.

### Request Instructions

Use the **Instructions** tab to provide guidance that requestors see before beginning a new Relay request.

Instructions can help communicate your organization's intake expectations before a request is submitted.

For example, you may ask requestors to:

* Provide a case number or matter name
* Describe the requested forensic work
* Include relevant supporting documentation
* Provide detailed evidence information
* Identify relevant contacts
* Follow specific physical evidence delivery procedures

Clear instructions can help reduce incomplete submissions and unnecessary follow-up during intake.

{% hint style="info" %}
Keep request instructions focused on what the requestor needs to know before submitting. This is a good place to explain required documentation, evidence drop-off procedures, intake expectations, or other organization-specific requirements.
{% endhint %}

<figure><img src="https://2683670198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCD1iskOdIm8E2TpCd9iZ%2Fuploads%2F2QvPv8Mk3AkDOPJsRldL%2Frelay-instructions.png?alt=media&amp;token=006928a6-2c61-478c-b4a4-4db8c8068672" alt=""><figcaption></figcaption></figure>

### Custom Field Options

Relay provides a standardized request workflow while allowing organizations to expose supported custom fields when additional information is needed.

Use **Custom Field Options** to control which configured Inquiry and Evidence custom fields appear to Relay requestors.

Custom Inquiry fields can also be mapped to Custom Case fields so information collected during request intake can carry forward when the Inquiry becomes a Monolith case.

This is useful for collecting organization-specific information without maintaining a separate intake form.

See [**Custom Field Options**](#custom-field-options) for setup instructions.

### Relay Administration and Monolith Users

Relay and Monolith currently use separate user accounts.

A Monolith administrator can configure Relay from **Settings > Relay Settings**, but Monolith access alone does not automatically provide access to the Relay application.

If a Monolith user needs to:

* Review requests directly in Relay
* Access **All Requests**
* Communicate with requestors through Relay Comments
* Use @mentions
* Perform Relay administrative actions

that user should also have a Relay account with the appropriate Relay permissions.

{% hint style="info" %}
For teams actively using Relay, consider ensuring that the Monolith users responsible for request triage also have the appropriate Relay access. This allows them to move between Monolith's Inquiry workflow and Relay's request communication tools when needed.
{% endhint %}

### Relay Authentication

Relay uses its own authentication system separate from Monolith.

Organizations can use the standard Relay username and password workflow or configure Single Sign-On (SSO).

Relay SSO is configured separately from Monolith SSO, even when both applications use the same identity provider.

See [**Single Sign-On (SSO)**](/monolith/start-here/welcome-to-monolith/sso-login.md) for additional information.

### Recommended Setup Order

When configuring a new Relay tenant, a practical setup sequence is:

1. Configure **Basic Details** and confirm the Relay tenant URL.
2. Make sure the Monolith users who will administer or communicate through Relay also have Relay accounts with the appropriate permissions.
3. Configure **Request Instructions** for your intake process.
4. Review **Custom Field Options** and enable any additional information your team wants to collect.
5. Invite a small group of test users.
6. Submit a test request through Relay.
7. Confirm that the request appears correctly under [**Case Management > Inquiries** ](/monolith/relay-request-portal/relay-overview/managing-relay-requests-in-monolith.md#review-inquiries)in Monolith.
8. Review the complete request-to-case workflow before distributing the Relay URL broadly.

Testing the workflow from both the requestor and forensic-team perspectives can help identify missing instructions, fields, or access requirements before wider adoption.

### Related Documentation

* [**Relay Overview**](/monolith/relay-request-portal/relay-overview.md)
* [**Using Relay**](/monolith/relay-request-portal/relay-overview/using-relay.md)
* [**Managing Relay Requests in Monolith**](/monolith/relay-request-portal/relay-overview/managing-relay-requests-in-monolith.md)
* [**User Management**](/monolith/relay-request-portal/relay-overview/relay-administration/user-management.md)
* [**Custom Field Options**](#custom-field-options)
* [**Single Sign-On (SSO)**](/monolith/start-here/welcome-to-monolith/sso-login.md)
