Users with the System Administrator permission can configure various aspects of the EDR module, including file storage paths, clustering behavior, deduplication settings, folder structure in Document Management, and tag customization.
NOTE: All Root paths must be unique and must be created on the server before configuring EDR. Each Root folder must be shared with Read/Write permissions for the application service account.
Steps to Configure Electronic Document Review (EDR)
Click Administration > Electronic Document Review (EDR) > EDR Configuration. The EDR Configuration screen displays as shown below.
.png?sv=2022-11-02&spr=https&st=2026-04-30T14%3A32%3A10Z&se=2026-04-30T14%3A46%3A10Z&sr=c&sp=r&sig=bCq4T2wFTzgTWf%2FFrBspUO2CYbDCsGy3V279AzZgBwU%3D)
Enter information in the fields described below as needed:
EDR Configuration Fields
Field | Description |
File extensions to exclude from indexing | Files with extensions listed in this field will be excluded from indexing. Users can add new extensions or remove existing extensions as needed. |
Data Path Root | The location where data files are stored. |
Index Path Root | The location where indexed files are stored. |
Text Path Root | The location where text files are stored. |
Reports Path | The location where reports are stored. |
Temp Path | The location where temp files should be written when ingesting a dataset into EDR |
Pro Tip: Use a consistent naming convention for your path folders (for example, \\ServerName\EDR\Data, \\ServerName\EDR\Index, etc.) to simplify administration and troubleshooting.
Cluster Settings
Clustering organizes documents into groups based on shared content, which helps reviewers identify related documents more efficiently.
Field | Description | When to Use |
Enable Clustering | When selected, this option organizes and identifies files on the hard drive. | Enable this option when your dataset contains a large volume of documents, and reviewers need to identify groups of related content. If your dataset is small or documents are unrelated, clustering may not provide a significant benefit. |
Create email Containment Clusters | Provides the option to view which documents/emails are contained within other documents/emails | Enable when processing email datasets where it is important to understand the relationship between emails and their attachments or embedded content. |
Relevancy Cluster | Clusters documents using relevant shared data such as common terms, phrases, or metadata. | Enable when reviewers need to identify documents that are conceptually similar, even if they are not exact duplicates. Useful for large review sets with diverse document types. |
NOTE: Clustering runs during data source processing and may increase processing time depending on the size of the dataset.
Folder Structure in Document Management (DM)
These settings control how documents appear in Document Management after they are processed through EDR.
Field | Description | When to Use |
Add Each Document to Document Management as an Individual Folder | Each document appears in its own folder in DM. You can select the Do not create a section in the Individual Folder checkbox to skip section creation inside each folder. | Use when each document requires its own distinct folder - for example, when documents are reviewed individually and need separate tracking. |
Add All the Documents into one folder, separated by Sections | All documents are placed in a single DM folder, with each document appearing in its own section within that folder. | Use when documents should be grouped together - for example, when all documents from a single data source should be reviewed as a set. |
Data Source Processing Settings
Deduplication
Deduplication identifies and flags duplicate documents within the dataset.
Fields | Description | When to Use |
De-dup across all document types | Find duplicates and near-duplicates across all document types. Excludes metadata from the comparison. Requires clustering to be enabled. | Choose this option when you want the broadest deduplication coverage, including near-duplicates. Useful when your dataset contains documents in multiple formats that may have the same content (for example, a Word document and a PDF with identical text). |
De-dup by document type | Find exact duplicates within each document type. Includes metadata in the comparison. Does not require clustering. | Choose this option when you only need to identify exact duplicates within the same file type. This is faster than cross-type deduplication and is suitable for datasets where documents are primarily in a single format. |
Email Attachment Handling
Field | Description | When to Use |
Keep email body and attachments as separate documents | Attachments will be separated from emails for deduplication; association to the parent email will be retained. | Choose this option when attachments may also exist as standalone documents in the dataset, and you want to deduplicate them against those originals. |
Keep the email body and attachments as a single document | Attachments will be appended to the parent email and will not be deduped against original document types. | Choose this option when you want to preserve the original email structure and review emails with their attachments together as a single unit. |
Tag Colors
Use this section to create and manage custom tags for use in EDR document review.
To add a new tag:

Field | Description |
Tag Colors | Use the fields provided to add custom tags as needed. To add a new custom EDR tag, click Add Tag. New fields appear to capture the tag Name, Color, and there is also the option to Delete a tag under the Actions column. Custom tags are available for use in EDR. (!!) Note: The Not Reviewed tag cannot be edited (!!) Note: System tags cannot be deleted |
Click Save. A confirmation message displays as shown below.

Click OK.
NOTE: When the configuration is saved, it cannot be canceled or "turned off," however, the System Administrator can manually remove the EDR configurations in the database.