Vault Custom Fields

What's Coming

Vault will support custom fields: your own columns in a vault's file explorer, so teams can label, organize and filter document sets by jurisdiction, practice area, matter phase, reviewer or deal name. Custom document types (your own values in the Document Type column) will follow at general availability. During early access, the Document Type column keeps showing Harvey's built-in, AI-inferred classifications.

Feature Highlights

Early Access

• Create your own columns: add a custom field from the table header or a file's side panel, and set its type to a label (single- or multi-select), a Person or a Date.
• Assign values: set a value on one file, or select several files and apply a value at once.
• Set the vault's view: reorder or hide columns; Vault saves these display settings for everyone with access. Column widths reset each session for now.
• Filter and sort: narrow the file explorer by field values before running a query or review, e.g. filter a contract repository to a single jurisdiction.
• Permission-aware: everyone with vault access can see custom fields. Assigning values needs Editor or above; creating a field needs Owner, Full access or Workspace Admin. The workspace audit log records every field change.

General Availability

• Custom document types: create and manage your own document type values (e.g. "Witness Statement" or "Convertible Loan Agreement") at the workspace level from the Command Center.
• Workspace-level fields: share one field taxonomy across vaults instead of defining it per vault.
• Self-serve CSV import and AI-assisted tagging: during early access, bulk import from tools like Kira, Relativity or iManage runs as a Harvey-assisted migration.

FAQs

Q: Can I add my own document types during early access?
A: Not yet. In early access the Document Type column keeps showing Harvey's AI-inferred classifications. Creating your own document types arrives at general availability.

Q: Can I bulk-import my firm's existing tags from Relativity, Kira or iManage?
A: Not self-serve. During early access, Harvey runs bulk imports as an assisted migration; self-serve CSV import arrives at GA.

Q: Do custom field values carry over if I move a file to a different vault?
A: No. Fields belong to a single vault, so a file loses its values when moved. Workspace-level fields, shared across vaults, are planned for GA.

Q: Will Harvey apply values to new documents for me?
A: Not in this release. You apply custom fields manually; AI-assisted bulk assignment is planned for GA.

Q: Can I use custom fields to scope an Assistant or agent query?
A: Not at launch. Filtering and sorting work in the Vault file explorer only. Query-time filtering by field value is a stated goal but sits outside this release.

Q: Can I change a field's type after creating it?
A: No. A field's type is fixed once created; to use a different type, create a new field.

Q: What happens if I delete a field value?
A: Deleting a value removes it from every file that had it, with no deactivate or soft-delete. Fields also have limits: up to 20 tags per document, 1,000 per vault, and a flat structure with no parent/child hierarchies.