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

# Integrations

Monolith supports integrations that connect specific workflows with external systems and services.

Available integrations may require additional configuration or administrative access to the corresponding external service.

### Forensic Partner Reports

The **Forensic Partner Reports** integration supports organizations that report forensic Case and Evidence metrics to the United States Secret Service.

The integration can help map Monolith Case Types and Evidence Types to the corresponding categories used for Forensic Partner Reporting and provides an Excel report containing the applicable metrics.

The generated report can be used to review and transfer reporting information according to your organization's USSS reporting process.

When enabled, the integration may also create supporting Custom Fields used to capture information required for the report.

<figure><img src="/files/nBPXbmDyZQUApyV9FWpE" alt=""><figcaption><p>Forensic Partner Reports</p></figcaption></figure>

### Mattermost

The **Mattermost** integration allows supported Monolith notifications to be sent to a Mattermost channel.

This can help teams surface Monolith activity within an existing Mattermost collaboration environment.

Configuration requires access to the Mattermost environment where notifications will be delivered.

### Microsoft 365 Admin

The **Microsoft 365 Admin** integration connects supported Microsoft 365 directory workflows with Monolith.

Depending on the workflow, Microsoft 365 directory information can be used to help populate or import records such as users and people information rather than entering each record manually.

This can be particularly useful for organizations that already maintain employee, requestor, or contact information in Microsoft 365.

See [**Team Management**](/monolith/using-monolith/organization/team-management.md), [**Clients**](/monolith/using-monolith/people/clients.md), and [**Contacts**](/monolith/using-monolith/people/contacts.md) for more information about how these records are used in Monolith.

### Google Workspace Admin

The **Google Workspace Admin** integration provides similar directory-based workflows for organizations using Google Workspace.

Supported directory information can be used to help populate Monolith records such as users and people information, reducing duplicate data entry when that information is already maintained in Google Workspace.

See [**Team Management**](/monolith/using-monolith/organization/team-management.md), [**Clients**](/monolith/using-monolith/people/clients.md), and [**Contacts**](/monolith/using-monolith/people/contacts.md) for more information.

### Choosing an Integration

Integrations are intended to extend specific Monolith workflows rather than being required for normal use of the platform.

Organizations may choose to configure integrations when they already use the corresponding external service or when the integration reduces duplicate data entry, improves collaboration, or supports an existing reporting requirement.

### Related Documentation

* [**Team Management**](/monolith/using-monolith/organization/team-management.md)
* [**Clients**](/monolith/using-monolith/people/clients.md)
* [**Contacts**](/monolith/using-monolith/people/contacts.md)
* [**Cases**](/monolith/using-monolith/case-management/cases.md)
* [**Evidence Items**](/monolith/using-monolith/evidence-management/evidence-items.md)
* [**Custom Fields**](/monolith/using-monolith/settings/custom-fields.md)