February 7, 2025: Batch Translate and Store Non-English Language Text, Organization User Management Improvements, and More!

With this release, we’ve added the ability to batch translate and store non-English text 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:

Everlaw Translate: Batch translate and store non-English language text

Everlaw now supports batch translation and translation storage for non-English language text for organizations that have purchased Everlaw AI credits. This functionality is enabled at the project level and allows you to:

  • Batch translate non-English documents
  • Search documents based on their stored translated text
  • Batch export stored translations as text files
  • Avoid the need for repeated translations whenever you view a document

Translations can be created by batch in the results table or created per document in the review window. They can also be exported as needed. It is a feature add-on requiring Everlaw AI credits.

This feature does not replace the existing option to translate non-English language text ad hoc. The existing translation tools for single documents are still available at no additional cost.

Note

To learn more about purchasing credits for Everlaw Translation, please speak to your Everlaw Customer Success Manager or request a call.

Note

The ability to batch translate and store non-English text is not available in Everlaw GovCloud. To learn more, read this article about Everlaw GovCloud.

Learn more in our article Batch Translate and Store Non-English Language Text.

Language detection improvements

We made some internal adjustments to how Everlaw detects non-English language characters. This allows for the following improvements:

  • Project Admins no longer need to specify which non-English languages should be detected (Expected Languages)
  • The Language search term now lists all languages detected to be present in all of the uploaded documents in the project, and allows you to search for any non-English language document
  • We’ve significantly increased the number of non-English languages that Everlaw can detect. For a complete list of supported languages, visit Supported non-English languages

Organization user management improvements

Org Admins are typically responsible for administering and managing all the users with access to their Everlaw data. 

With this release, Everlaw has introduced several reporting and user management improvements at the organization-level:

  • Increased visibility into users on any Everlaw project within their organization from the Organization home page
  • The ability to share work product when removing users from the organization
  • More information about users, including last project login, to the platform and CSV export.

Learn more in our article on Organization and Project Administration.

Option to turn off binder notifications

Users can now specify whether or not they would like to send out a notification when sharing an existing binder.

Learn more in our article on Binders.

 

Updated reprocessing OCR options 

This release updates two aspects of the OCR options available when reprocessing documents from the results table:

  • Database Admins can now choose to Force OCR for PDFs/Images. Previously, this tool was only available to Organization Admins.
  • Database Admins and Organization Admins can now Flatten and Force OCR for PDFs

Learn more in our article on Reprocessing.

PDF embedded file detection during processed uploads

Everlaw now detects embedded files from “image” PDFs during processed uploads and identifies them with the processing flag Embedded Files in Image. This update resolves a common issue with Bates-stamped emails saved and uploaded as PDFs, where attachments were previously overlooked.

Learn more in our article Locating Uploaded Documents on Everlaw.

Include or exclude Slack attachments during upload and reprocessing 

You can now choose whether or not to fetch attachments during native upload of Slack data, either through Everlaw's cloud connection to Slack or through a Slack export. This gives you more control over the final data size of your Slack uploads. 

Learn more in our article Upload Documents from Slack.

Segment chat documents by 24 hour segments

During native upload of chat data, you now have the option to segment the chat documents into 24-hour segments. Previously, most chats were automatically segmented into 100-chat documents. With this release, you can select between these two options to segment your chat files. 

Learn more in our article Upload Native Data to Everlaw.

Administer users in API

Organizations using Everlaw's API can now administer Everlaw users at the project, database, and organization levels using the API. This includes adding and removing users and granting permissions.

Learn more in our article on Everlaw API.

Add deposition testimony directly to a Draft or Deposition 

Selected testimony can now be paired with a Draft or Deposition directly from the transcript text.

Learn more in our article in our article Deposition 3 of 4: Summary, Transcript, and Testimony.

Change in native upload details report

The Native upload report now includes Native size instead of Source size.
native size new.png

  • Native size is a sum of the native sizes of all the documents in this upload
  • Source size was calculated summing the sizes of the files uploaded, and did not count documents in the upload extracted during processing

The Source size values from previously exported reports are not comparable to those in the Native size column of new reports. You can export a new report that includes the new, Native size value for each of your previous uploads.
This change has no impact on billable size and does not change anything about your data on the Everlaw platform.

Change in Everlaw AI Assistant data locality for EU and UK clients

For Everlaw clients in our EU and UK environments, tasks for Everlaw AI Assistant are now solely processed in the Open AI EU region. No action is required from Everlaw users. 

Learn more in our Everlaw AI Assistant FAQ.

Visual improvements 

  • The button to stop a production in process now reads Abort
Before After
  • The language at the top of the production modification menu is updated. An additional sentence reminds users that "Any modifications desired in the produced documents should be made to the source documents."
Before
After
  • The production warning about redactions has been updated to better align with the production protocol step it refers to. It now reads "No redactions included in production."
Before After
  • The toast notification in Legal holds is updated to our current toast styling
Before After

_____

Do you have feedback about:

  • this release document? Submit your feedback
  • the features in this release? Email feedback@everlaw.com