> 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/case-management/cases/files.md). # Files Store, organize, review, hash, download, and securely share files and folders associated with a Monolith Case. Files provides a centralized file system for documents, exports, reports, screenshots, supporting material, and other files associated with a Monolith Case. Files can be uploaded directly by Monolith users or added through other workflows, including Relay intake and Note exports. Files and folders can also be shared with Relay users through [**Case Drives** ](/monolith/relay-request-portal/relay-overview/using-relay.md#case-drives)when information needs to be provided back to a requestor. ### Video Walkthrough {% embed url="" %} Case File System How-to Video. If the video does not render, [watch on YouTube here](https://www.youtube.com/watch?v=3m5cNpabstY) {% endembed %} ### View Case Files Open a Case and select the **Files** tab to access its file system. Case Files supports standard Monolith table functionality, including: * Search * Filtering * Sorting * Column selection * Exporting the file list to Microsoft Excel * Folder navigation Available columns include: * Action * UUID * Name * Type * Status * Size * Extension * Path * Created On * Client Modified * Created By * MD5 * SHA1 * SHA256 * Description Use the column selector to display the information most useful for your workflow. ### Organize Files and Folders Case Files behaves like a file system rather than a flat attachment list. Users can: * Create folders * Create nested folders * Upload files * Upload folders * Drag and drop files into the Files workspace * Move files between folders * Organize related Case material into a folder structure This allows a Case to hold a substantial amount of supporting material without requiring every file to remain in a single list. For example, a Case might organize files into folders for: * Search authority * Supporting documentation * Examination exports * Reports * Screenshots * Deliverables * Client-provided material * Other Case-specific work products ### Recursive View Enable **Recursive** to view files contained within nested folders without manually opening each folder. This can be especially useful when searching or reviewing a Case with a larger folder structure. Disable Recursive view when you want to work within the current folder only. ### Upload Files Use **New > Upload File** to add a file to the Case. Files can also be added through drag and drop. Use **Upload Folder** when an existing folder structure should be brought into the Case. Case Files are intended for general Case-related material, allowing teams to keep supporting documents and work products associated with the Case where they can be easily found later. {% hint style="info" %} File storage is part of your Monolith environment's available storage allocation. Organizations working with particularly large datasets should consider whether the Case Files area or another storage workflow is most appropriate for that data. {% endhint %} ### Hash Files During Upload {% embed url="" %} If the video does not render, you can [watch directly on YouTube here](https://www.youtube.com/watch?v=hHiRa3jLxUM) {% endembed %} Enable **Hash Uploads** when Monolith should calculate hash values for files as they are uploaded. Supported file metadata includes: * MD5 * SHA1 * SHA256 Hashing can provide additional integrity information for files retained with the Case. {% hint style="info" %} Calculating hashes requires Monolith to process the uploaded data and may increase upload time, particularly for larger files. {% endhint %} ### Search and Filter Files Use **Search Files** to locate files within the Case. Search can use information such as the file name and Description, making descriptive file metadata useful as the number of Case Files grows. Filters can also be applied using supported File fields such as: * UUID * Name * Type * Status * Size * Extension * Path Combined with folders and Recursive view, these tools make it easier to locate material within larger Cases. ### File Details Select **Show Details** from a file's action menu to review additional information about the file. Available details may include: * UUID * Name * Type * Status * Size * Extension * Path * Created On * Client Modified * Created By * MD5 * SHA1 * SHA256 * Shared With * Description Descriptions can provide useful additional context about why a file is part of the Case or what it contains. ### File Activity The File Details view also includes an **Activity** section. Activity provides a history of supported actions associated with the file, including activity such as: * Viewing the file * Downloading the file * Other supported file interactions Entries identify the user associated with the activity, when the action occurred, and whether it was accessed within Monolith or within the Relay Request Portal. This provides additional context around how Case Files have been accessed over time. ### View and Download Files Use the file action menu to work with an individual file. Available actions include: * **Show Details** * **Share via Relay** * **View Item** * **Edit** * **Download** * **Delete** **View Item** allows supported files to be opened or previewed from Monolith. Use **Download** when a local copy of the file is needed. ### Edit File Information Use **Edit** to update supported File information such as the Description. Adding a meaningful Description can make files easier to identify through search and provides additional context beyond the filename alone. ### Delete Files Use **Delete** when a file should be removed from the Case. Monolith prompts for confirmation before completing the deletion. {% hint style="warning" %} Confirm that the file is no longer required before deleting it from the Case. {% endhint %} ### Files Added From Other Monolith Workflows Not every Case File begins with a manual upload. Files may also enter the Case through other Monolith workflows. #### Relay Inquiry Documents Documents submitted with a Relay request can be carried into the resulting Case when the Inquiry is converted or merged. Once imported, those documents become normal Case Files and can be organized alongside other Case material. See [**Inquiries**](/monolith/using-monolith/case-management/inquiries.md) and [**Managing Relay Requests in Monolith**](/monolith/relay-request-portal/relay-overview/managing-relay-requests-in-monolith.md) for more information. #### Note Exports When a Note is exported to PDF or Microsoft Word, Monolith also adds the generated document to the Case Files area. This allows exported examination Notes to remain with the Case alongside other documents and work products. See [**Notes**](/monolith/using-monolith/case-management/cases/notes.md) for more information. #### **Evidence Files** Each Case has a folder named **Evidence Files**, kept by Monolith. An Evidence Item gets a folder only after it receives its first file. Monolith names that folder with the item's Evidence Number. It holds that item's photos and other files. Files in an item's folder are the same files shown on the Evidence Item's **Files** and **Photos** tabs. A change in one place shows up in the others. Files can be uploaded into an item's folder, renamed, described, shared, and deleted like other Case Files. The **Evidence Files** folder and the item folders themselves can't be renamed, deleted, or moved, and new folders can't be created inside them. See [**Evidence Files**](/monolith/using-monolith/evidence-management/evidence-items.md#evidence-files) for more information. ### Share Files Through Relay Case Files can be shared with Relay users through **Case Drives**. Select **Share via Relay** from the file action menu to make appropriate Case material available to one or more Relay users. Files and folders can be shared with multiple Relay users as needed. For each user, Relay provides a Case Drive associated with the Monolith Case and the content that has been shared with them. A typical workflow looks like: ``` Case File or Folder ↓ Share via Relay ↓ Select Relay User(s) ↓ Case Drive Available in Relay ↓ Requestor Accesses Shared Content ``` This can be useful for sharing: * Reports * Deliverables * Supporting documents * Exported data * Other Case-related files #### Video Walkthrough {% embed url="" %} If the video does not render, [watch directly on YouTube here](https://www.youtube.com/watch?v=zU2B9PDf_Ms) {% endembed %} ### Manage Relay Sharing Sharing a file through Relay does not move or remove the original file from the Monolith Case. Sharing can later be removed when the Relay user should no longer have access to that content. Removing the share does not delete the underlying Case File. File details also provide information about users the file has been shared with, allowing the forensic team to review its sharing history. {% hint style="info" %} Case Files remain controlled from Monolith. Relay Case Drives provide access to specifically shared content rather than exposing the entire Case file system to the requestor. {% endhint %} See [**Case Drives**](/monolith/relay-request-portal/relay-overview/using-relay.md#case-drives) for the Relay user experience. ### Export the File List Use **Export List to XLSX** to export the current Files table to Microsoft Excel. As with other Monolith tables, the export reflects the current table configuration, including the selected columns and applicable filtering. This can be useful for reviewing or providing an inventory of files associated with a Case without downloading the files themselves. ### Files as Part of the Case Record Case Files provide a central location for the documents and supporting material associated with Casework. A Case may accumulate material from: * Manual uploads * Relay request Documents * Note exports * Examiner work products * External reports * Screenshots * Supporting documentation * Final deliverables Folders, descriptions, search, hashes, and activity history allow that material to remain organized and connected to the Case rather than being maintained across unrelated file shares or local folders. ### Recommended Practices * Keep Case-related documents and work products associated with the Case when practical. * Use folders to organize larger collections of Case Files. * Use descriptive filenames and Descriptions so files remain easy to locate later. * Use Recursive view when reviewing files across nested folders. * Enable Hash Uploads when file hash values are useful to your workflow. * Be aware that hashing large files can increase upload processing time. * Review File Details when additional metadata or activity history is needed. * Share only the files or folders a Relay requestor should have access to. * Remove Relay sharing when access is no longer appropriate without deleting the underlying Case File. * Use Case Drives when providing reports, deliverables, or other files back to Relay users. * Consider available tenant storage when deciding whether particularly large datasets should be stored in Case Files. ### Files Extended Walkthrough A recorded Monolith Mondays session covering the full File system workflow, including the topics described above. {% embed url="" %} If the video above does not render, [watch directly on YouTube here](https://www.youtube.com/watch?v=VREgn7ctipQ) {% endembed %} ### Related Documentation * [**Cases**](/monolith/using-monolith/case-management/cases.md) * [**Notes**](/monolith/using-monolith/case-management/cases/notes.md) * [**Inquiries**](/monolith/using-monolith/case-management/inquiries.md) * [**Managing Relay Requests in Monolith**](/monolith/relay-request-portal/relay-overview/managing-relay-requests-in-monolith.md) * [**Using Relay**](/monolith/relay-request-portal/relay-overview/using-relay.md) * [**Case Drives**](/monolith/relay-request-portal/relay-overview/using-relay.md#case-drives) * [**Evidence Files**](/monolith/using-monolith/evidence-management/evidence-items.md#evidence-files)