Expected AU release: September 1, 2026 ACT
Expected release for all other: September 2, 2026 PT
Knowledge Base updates: September 2, 2026
With this release, we've added a native chat review experience, a new option to extract chat images as attachments, a password bank for native uploads, and more — read on for more information about the features coming out this month! If you would like to learn more about the features in this release, join us for a live training session.
User-facing features in this release:
- Native chat review experience
- Extract chat images as attachments during native upload
- Password bank for native uploads
- Ask Deep Dive questions from Claude
- Filter Coding Suggestions category and Rationale columns in results tables
- Send file transfers directly to the processed uploader
- Refine case descriptions
- SharePoint "classic" links are now detected in Purview uploads
- Include Gemini data with your Google Vault data preservations
- New last-login details in Database Sizes exports
- Staging Drive size in the billing API
- Choose whether custodians must acknowledge a legal hold notice
- Visual improvements
Note
Tell us about your role
At your next login, you'll see a quick prompt asking for your job role. This will help us customize Everlaw for all our users, new and existing. If none of the options fit, just pick Other and tell us what you do.
This is a one-time survey, and your selections are not listed in your account settings.
Native chat review experience
Everlaw now supports a native review experience for chat data. Long conversations are still separated into multiple documents on upload, but the new Chat view in the review window lets you scroll through every segment in one place — so you can follow a conversation the way it looked in its original application, and keep important context while you review.
Chat data from Cellebrite, Slack, Teams, RSMF, Google Hangouts, Bloomberg emails, iMessage, and iOS WhatsApp databases is supported. Hit highlights, redactions, and highlights are not available in Chat view.
Extract chat images as attachments during native upload
During native upload, you can now choose whether images inside chat data are extracted as separate attachments or left displayed in line only. Extracting them makes each image reviewable on its own — so you can run Coding Suggestions against it separately from its parent chat document, or add it to a Story when the surrounding conversation isn't relevant.
Databases default to extracting images. Extracted images count toward your database's billable size.
Password bank for native uploads
Everlaw can now store a bank of passwords at the database level, available during native upload, reprocessing, and when adding files to an existing dataset. Instead of keeping a list outside the platform and pasting from it each time, your team enters each password once and reuses it for the life of the database.
Ask Deep Dive questions via MCP server
Two new Everlaw MCP server tools, AskDeepDiveQuestion and GetDeepDiveResponse, let you ask Deep Dive questions from within MCP servers, like Claude — so you can research a project without switching tools. The project must be enrolled in Deep Dive.
Filter Coding Suggestions category and Rationale columns in results tables
You can now filter any Coding Suggestions category column or Rationale column in a results table, narrowing your results to just the suggestions you care about. Category columns support advanced filtering, and Rationale columns support keyword filtering, including advanced content searching.
Send file transfers directly to the processed uploader
For Partners and teams that use file transfers to direct processed uploads to their admins for upload onto Everlaw: You can now direct file transfers straight to the processed uploader. This saves the effort and time of downloading and then reuploading the transferred files, which makes uploading file transfers easier and faster.
This new functionality is available from two places:
- On the file transfer card (Uploads > File transfers, select the three-dot menu > Send to processed uploader.
- When you start a new processed upload, select Upload a file transfer. From here, you'll pick which one to use.
Then, you'll proceed to the processed uploader as normal.
Important considerations
- The file transfer must be zipped to be eligible to send to the processed uploader
- Sending a file transfer to the processed uploader does not update its status on the card; status updates must still be done manually
Refine case descriptions
Project Admins can now use the AI Enhance button to refine an Everlaw AI case description — improving its grammar, clarity, and organization while preserving the dates, parties, claims, and other substantive details already in it.
A new Show tips option flags information gaps worth filling, which improves how well downstream features like Deep Dive and Coding Suggestions understand your case.
SharePoint "classic" links are now detected in Purview uploads
Everlaw now detects "classic" SharePoint links during Purview uploads. This SharePoint link format is used in some Purview collection formats to connect modern attachments for chat data. This improvement means that more modern attachments (linked documents) are detected and connected properly in Everlaw.
Include Gemini data with your Google Vault data preservations
Google Vault now supports preserving Gemini data, and Everlaw's Google Vault data preservation tool has been updated to match — you can select Gemini as a data source when you create a preservation.
New last-login details in Database Sizes exports
Organization Admins can now include the name and date of the most recent admin and non-admin login in Database Sizes exports, using four new optional fields:
- Last Non-Admin Login User
- Last Non-Admin Login Date
- Last Admin Login User
- Last Admin Login Date
This makes it easier to distinguish admin activity from reviewer activity and identify dormant databases that may be candidates for archival or deletion — without requesting a custom report.
Staging Drive size in the billing API
Everlaw’s billing API now returns Staging Drive size for an organization, and Parent Organization Admins can retrieve it aggregated across sub-organizations. This lets you monitor Staging Drive usage and include it in external billing or capacity dashboards alongside your other organization-level billing data.
Choose whether custodians must acknowledge a legal hold notice
Legal Holds Admins can now choose whether custodians are required to acknowledge a hold notice. Custodians still receive the notice either way, but when acknowledgment isn't required they skip the acknowledgment portal workflow, their status shows as "Not required" rather than as awaiting acknowledgment, and follow-up workflows like re-notifications and escalations don't run. Acknowledgment is required by default.
Visual improvements
- Partial project suspension is now called "Disable project access." The new name better reflects what the action does: restrict access to documents and prevent modifications to review work. Going forward, "suspend" refers exclusively to suspending a full database, which remains the only way to change what's being billed.
| Before |
| After |
- The Legal Hold Questionnaires Edit questionnaire dialog has the following changes:
- The right side panel is now open by default
| Before |
| After |
- The Question tab starts with a page one, rather than just showing an add button
| Before |
| After |
- The right side panel’s CONDITIONS section is now called LOGIC.
| Before |
| After |
- The Question types options have been condensed to simplify your choices: Short text and Long text have been merged into one Text type, and Date range has been folded into the Date type. The Multiple choice option has also been renamed to Radio group.
| Before |
| After |
- The Preview page no longer displays the Complete button that recipients will see
| Before |
| After |
Do you have feedback about:
- this release document? Submit your feedback
- the features in this release? Email feedback@everlaw.com