> 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/using-monolith/settings/custom-fields.md).

# Custom Fields

Custom Fields allow your organization to capture structured information that is specific to your workflows but is not part of Monolith's standard fields.

Custom Fields can be created for:

* Cases
* Evidence Items
* Inquiries
* Acquisitions
* Storage Items
* People

**Custom People Fields** apply to both Clients and Contacts.

For example, an organization might use Custom Fields to capture legal authority, internal department, examination type, handling requirements, matter classifications, employee identifiers, agency information, or other information relevant to its work.

### Custom Field Settings

The **Custom Fields** settings page allows administrators to create, edit, enable, disable, reorder, and delete Custom Fields for each supported record type.

Custom Fields appear in the applicable Create and Edit forms throughout Monolith.

The available sections include:

* **Custom Case Fields**
* **Custom Evidence Fields**
* **Custom Inquiry Fields**
* **Custom Acquisition Fields**
* **Custom Storage Fields**
* **Custom People Fields**

### Add a Custom Field

Open the section for the record type where you want the field to appear, such as **Custom Case Fields**, **Custom Evidence Fields**, or **Custom People Fields**.

When creating a Custom Field, configure the following options:

1. **Field Name** — the name displayed to users in Monolith.
2. **Is Required** — determines whether users must provide a value when creating or editing the applicable record.
3. **Editor Type** — determines how users enter the value.
4. **Description** — provides placeholder or guidance text within the field.

{% hint style="warning" %}
A Custom Field's Editor Type cannot be changed after the field is created. The field can still be enabled, disabled, reordered, edited, or deleted.
{% endhint %}

### Editor Types

Available Editor Types include:

* **Textbox** — standard text entry
* **Date** — date selector
* **Drop Down Menu** — select one value from a predefined list
* **Tag Box** — select multiple values from a predefined list

Choose the Editor Type based on how you want users to enter and standardize the information.

For information that will frequently be filtered or reported on, predefined selections such as Drop Down Menu or Tag Box can help keep values consistent.

### Custom People Fields

**Custom People Fields** allow your organization to capture additional structured information about Clients and Contacts.

A Custom People Field is shared across both record types, meaning the same field can appear when working with either a Client or a Contact.

These fields can be useful for information such as:

* Internal or external identifiers
* Department or business unit
* Agency information
* Employee or custodian information
* Matter-specific classifications
* Organization-specific contact details
* Other information your team consistently tracks about people

Use **Custom People Fields** when the information applies to people records generally rather than to a specific Case, Evidence Item, or Acquisition.

See [**Clients**](/monolith/using-monolith/people/clients.md) and [**Contacts**](/monolith/using-monolith/people/contacts.md) for more information about how people records are used throughout Monolith.

### Manage Custom Fields

Existing Custom Fields can be managed from their applicable section.

#### Enable or Disable

Enable or disable a field to control whether it appears in Create and Edit forms.

Disabling a Custom Field does not remove previously stored values from records that already contain data for that field.

{% hint style="info" %}
For example, if an Evidence Custom Field called **Agency ID** is disabled, Evidence Items that already contain an Agency ID value will continue to retain that information. To permanently remove the Custom Field and its stored values, the field must be deleted.
{% endhint %}

#### Edit

Use **Edit** to update supported Custom Field settings such as the name, description, required setting, or available selection options.

The Editor Type cannot be changed after creation.

#### Delete

Deleting a Custom Field removes the field and its associated values from your Monolith tenant.

Review existing use of the field before deleting it.

{% hint style="warning" %}
Deleting a Custom Field is different from disabling it. Disable a field when you want to stop using it while preserving previously recorded values.
{% endhint %}

### Reorder Custom Fields

Custom Fields can be reordered within each record category by dragging and dropping them into the preferred position.

The configured order determines how the fields are presented to users within applicable Monolith forms.

Arrange commonly used or important fields near the top so they are easier to find during data entry.

### Custom Fields and Relay

Organizations using Relay can expose supported **Inquiry** and **Evidence** Custom Fields to requestors.

Inquiry Custom Fields can also be mapped to corresponding Case Custom Fields so selected information can carry forward when an Inquiry is used to create a new Case.

Relay visibility and field mapping are configured under **Settings > Relay Settings > Custom Field Options**.

See [**Custom Field Options**](/monolith/relay-request-portal/relay-overview/relay-administration/custom-field-options.md) for complete Relay configuration guidance.

### Custom Fields and Item Labels

Supported Custom Field values can also be used in Monolith label templates where applicable.

See [**Item Labels**](/monolith/using-monolith/settings/item-labels.md) for supported Custom Field label variables and syntax.

### Recommended Practices

* Use Custom Fields for information that is meaningful to your organization's workflow.
* Choose the Custom Field category that matches where the information belongs.
* Use Custom People Fields for information that should be available on both Clients and Contacts.
* Prefer structured selection fields when consistent values will improve filtering or reporting.
* Use clear field names and descriptions so users understand what information should be entered.
* Avoid creating duplicate fields that capture the same information in slightly different ways.
* Consider whether a field should be required before making it mandatory for every applicable record.
* Disable fields when they are no longer needed but historical values should be preserved.
* Delete fields only when the field and its stored values are no longer required.
* Order fields according to how frequently or early they are used in the workflow.

### Related Documentation

* [**Cases**](/monolith/using-monolith/case-management/cases.md)
* [**Inquiries**](/monolith/using-monolith/case-management/inquiries.md)
* [**Evidence Items**](/monolith/using-monolith/evidence-management/evidence-items.md)
* [**Storage Items**](/monolith/using-monolith/evidence-management/storage-items.md)
* [**Clients**](/monolith/using-monolith/people/clients.md)
* [**Contacts**](/monolith/using-monolith/people/contacts.md)
* [**Custom Field Options**](/monolith/relay-request-portal/relay-overview/relay-administration/custom-field-options.md)
* [**Item Labels**](/monolith/using-monolith/settings/item-labels.md)