Last date modified: 2026-Aug-12
Smarsh data source (Advanced Access)
The functionality described in this
This topic provides details on how to capture Smarsh archive data with Collect.
Considerations
Before connecting the Smarsh data source to Collect, consider the following:
- You create your data set as cases in Smarsh before connecting to Collect.
- Collect imports these cases directly.
- You do not need to configure custodians in the collection.
- For more information, see Prerequisites.
- More than one case can b exported at a time.
- You can import one smarsh case per collect job.
Prerequisites
Before you configure a Smarsh data source in Collect, your Smarsh instance must have an API client. To create or obtain an API client, contact your Smarsh administrator or Smarsh Support. When requesting the API client, confirm it has the scopes for case access and data export.
Record the following values when the API client is created. You enter them when configuring the data source in Collect:
- Client ID
- Client secret
- Smarsh tenant Base URL
Follow Smarsh's instructions to create a case and gather the required connection information before configuring the data source in Collect.
The Client Secret appears only when the API client is created and cannot be retrieved later. Store it securely. If you lose the secret, generate a new one in Smarsh.
Creating the data source in Collect
The Collection Admin tab is where you create, edit, and remove data sources from your workspace. You only need to set up each data source once. You must create your data sources before setting up your custodian targets.
- In RelativityOne, navigate to Collect.
- Click New Collection Source Instance.
- Enter a unique name for the data source.
- Select Smarsh.
- Enter the required information in Settings. For more information, see Settings fields.
- Click Save.
After clicking Save, Relativity verifies the parameters and connectivity to the Smarsh data source.
- If successful, Collect saves the data source.
- If the connection fails, a message appears indicating that the connection failed. Verify that the values are correct and save again.
After setup is complete, the data source appears on the Collect Admin page.
Settings fields
To connect Relativity to the Smarsh data source, gather and enter the information for the following fields:
- Client ID—the unique Client ID assigned to your Smarsh account.
- Client secret—the Client Secret associated with your Smarsh account credentials.
- Base URL—the base URL of your Smarsh server instance. For example, https://archive.smarsh.com.
Actions console
The Actions console includes the following options for the Smarsh data source:
- Refresh Cases—adds new cases if they are added on the Smarsh side after initial setup.
- Validate Connection—verifies the credentials you entered are correct and the connection to Smarsh is active.
Configuring the data source in Collect
In RelativityOne, configure the data sources chosen in the Collection Details step.
Data source criteria
All filtering takes place in Smarsh. Your organization's case team applies filters when creating the Smarsh case. There are no additional filter criteria to configure in Collect for this data source.
You must register Relativity in Smarsh before using this data source. For more information, see Smarsh data source (Advanced Access).
Preview
Before running a collection job, use the Preview console to confirm the case contains what you expect. The preview shows the number of items in the case and the approximate size.
Verify that the numbers match what you see in Smarsh before starting the collection.
Monitor
After the collection starts, the Monitor view shows the current status of the export. The status updates as the export progresses and changes to Complete when the export finishes.
Output format
Collect retrieves Smarsh data as .eml files. Each .eml file contains a complete conversation. Smarsh handles conversation threading before delivery. No additional conversion occurs in RelativityOne.
Metadata fields captured
Smarsh stores and exports timestamps in GMT. Verify timestamp formatting meets your review requirements before processing collected data.