Upcoming Feature
Document-Level Client Matters & Ethical Walls
Client matter numbers now live at the file level — enabling multi-matter vaults where ethical walls automatically hide files each user isn't cleared to see, so firms can finally build the precedent collections they actually want without compromising governance.
What's Coming
Today, Harvey tracks client matter numbers at the resource level — every file inside a vault or thread inherits one matter, which makes single-matter resources work well and everything else break. A precedent vault spanning dozens of matters has been practically impossible to approve, because every file would inherit a single matter and expose it to everyone with access. File-level client matter numbers change that. Each file now carries its own matter, sourced from iManage sync, DMS metadata, or manual assignment — and ethical walls enforce against the file directly. In Assistant and Review Tables, users need access to every client matter involved to open the resource at all.
Feature Highlights
- Client matter numbers now live on individual files — one vault can hold documents from many matters
- Client matter metadata carries over automatically on iManage sync — governance travels with the file
- Client matters surface across file lists, attachment chips, the Sources panel, citation popovers, and the thread header
- Assistant and Review Tables use a restrictive view — users need access to every matter involved to open the resource
FAQs
Q: Can a single file be tagged to multiple client matters?
No. Each file carries exactly one client matter. A vault can hold files from many different matters, but each individual file maps to one.
Q: How does client matter metadata get assigned to a file?
Metadata can come from iManage sync, other DMS file metadata, or manual user assignment. iManage is the only sync-compatible DMS that exposes client matter today — PDFs and files without embedded metadata will need to be assigned manually.
Q: Does this affect how Spaces work?
Spaces still carry zero or one client matter — Spaces are not multi-matter. The file-level client matter update applies to Vault, Assistant, and Review Tables.