April 15, 2026: New Global Object Access Permission, Upload Compressed Folders for Processed Uploads, and More!

Avatar
[System] Everlaw Support

Expected AU release: April 14, 2026 ACT

Expected release for all other: April 15, 2026 ACT

Knowledge Base updates: April 15, 2026

With this release, we’ve added a new Global Object Access permission, the ability to use a compressed folder to start a processed upload, 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:

Upload compressed (zipped) processed upload folders

You can now upload processed uploads in a compressed/zipped state. Previously, the outer folder for a processed upload with a load file had to be dragged in or selected in an uncompressed state. For very large uploads, unzipping locally is time consuming and dependent on a user's computer system and network performance. Now that Everlaw accepts compressed processed uploads, you can directly upload compressed folders.

Learn more in our Upload Processed Data with a Load File article.

New Global Object Access permission

There is a new project-level permission to allow access to all work product objects created in a project. When granted, this permission allows users to access all objects (e.g. binders, Search Term Reports, Storybuilder Drafts, etc.) without them being proactively shared. Project Admins determine both which user groups are granted this permission and the level of access for each user group. Global Object Access enables users to seamlessly access all the materials necessary to oversee and collaborate on their Everlaw projects.

Included with global access:

  • Assignment Groups
  • Stories 
  • Storybuilder Drafts
  • Storybuilder Depositions
  • Binders
  • Search Term Reports (STRs)
  • Prediction Models
  • Homepage folders

Learn more in our User Groups and Project Permissions article.

Import facts from spreadsheets to Fact Timelines

If your team is building case chronology in a spreadsheet, you can now try out what your process looks like using Fact Management in Storybuilder!

Storybuilder users can now import spreadsheets into Fact Timelines to either create a new Timeline or add Facts to an existing one. This allows your team to avoid manual re-entry of Facts you’ve already organized into a spreadsheet or exported from a pre-existing Storybuilder Fact Timeline.

Learn more in our Storybuilder Fact Timelines article.

Edit Coding Suggestions criteria from the Coding Suggestions dialog

Everlaw AI Coding Suggestions now supports editing suggestion prompts directly from the Coding Suggestions configuration dialog accessed in the results table and review window. 

This change lets users adjust coding prompts without navigating back to project settings, while still respecting existing permissions and version history.

Learn more in our Everlaw AI Coding Suggestions article.

Everlaw Archive™ reactivation history improvements

Everlaw Archive now helps prevent unexpected reactivation fees and improves visibility into archive/reactivation history for each database. This change ensures that a database cannot be archived and reactivated more than once within the same month in a way that would generate multiple reactivation fees.

Learn more in our Everlaw Archive article.

Legal Holds information is available through the Everlaw API

The Everlaw API now exposes legal holds data, including hold status, custodians, and preservation details. This enables your team to:

  • Create centralized, automated reporting and dashboards: Pull legal hold information into internal tools and compliance dashboards without manual exports
  • Automate holds in external systems based on the hold’s status in Everlaw: Accessing legal hold information through the API makes it possible for your team to automate holds in external systems based on the hold’s status in Everlaw

Learn more about the Everlaw API in our Organization Admin: Everlaw API article.

Primary Organization display customization for Single Sign On (SSO) users

SSO users can now edit their Primary Organization on the Account Settings page. This extends the previous update that allowed SSO users to edit cosmetic profile fields (i.e. First Name, Last Name, Title) while keeping security‑sensitive fields like email and password locked to the identity provider or existing support workflows.

To learn about updating your account settings, see our Edit Your Everlaw Account Settings article.

Updated display of edited chat messages in the PDF viewer

Everlaw now standardizes how edited chat messages appear when you view or export chats as PDFs. Edited messages include clearer labels, a more intuitive version order, and a more accurate placeholder when message text is unavailable. This brings the PDF view closer to how chats appear in their source platforms (e.g. Slack or Microsoft Teams).

These changes apply automatically to the Everlaw review window’s PDF chat view and all Everlaw-rendered chat exports.

Additional field types for custom metadata overlays 

Metadata overlays using identity fields other than Bates or control #s now support additional field types, so you can align overlay targets more closely with the data you’re loading and searching on.

The new supported field types for overlays are:

  • Bates-type
  • Number-type
  • Address list–type
  • Address from–type
  • MD5-type
  • SHA1-type

You can assign these types when creating or editing custom metadata fields in Project Settings, then point your overlays at those fields as usual.

Learn more about overlays in our Overlaying Data article.

Improved connector upload status display

Native uploads initiated through a cloud connection to an external data source will now display a progress bar and status. This gives those doing uploads more transparency into what is happening with their uploads, which can help with troubleshooting errors and understanding the timing and progress of uploads.

Increase max batch size for Everlaw AI Review Assistant features

We increased the maximum size of Everlaw AI Review Assistant batch actions, including Coding Suggestions and Custom Extractions, from 20,000 to 250,000 documents so teams can run these actions across large datasets with far fewer batches.

Searchable set document count is displayed on Search Term Reports (STRs)

Search Term Report (STR) Searchable set now displays the document count of the searchable set, in addition to the  Searchable set including attachments and Total documents in project counts.

Previously it only displayed the Searchable set including attachments and Total documents in project counts.

Visual improvements

  • We have updated the style of the OCR options during reprocessing. The new menu lets you separately select a Force OCR option (Default or OCR optimized for English handwriting) and whether or not to flatten your PDFs (which should be rare).
Before
After
  • We have made several improvements to the notifications that pop up when review work, such as applying coding presets, is applied in the review window. In particular:
    • You will now only see the notifications relevant for the document you are reviewing. In the example below, a coding preset was applied to document #5245.1. Previously, notifications could persist when you moved from one document to the next. With this release, the notifications disappear as soon as you navigate to the next document.
Before
After
  • There is no longer a Changes saved notification. Applied review work is auto-saved when you move onto the next document or leave the review window. You are warned if your review work will not be saved for any reason, such as disconnected internet.

_____

Do you have feedback about:

Was this article helpful?
0 out of 0 found this helpful

Do you have feedback about this article? Let us know