March 7, 2025: Multiple redaction stamps per redaction, database usage notifications, and more!

Expected AU release: March 5, 2025 ACT

Expected release for all other: March 7, 2025 PT

Knowledge Base updates: March 7, 2025 PT

With this release, we’ve added multiple redaction stamps per redaction, database usage notifications, 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:

Add multiple redaction stamps per redaction

Users can now add multiple redaction stamps to redactions. This is helpful in scenarios in which there are multiple reasons for redacting content (e.g. multiple privilege or confidentiality reasons or multiple exemption codes).

This feature does not change the primary steps used to create or edit redactions; the only difference is that now you can select multiple stamps from a dropdown list, rather than the previous single selection.

Before After

 

Multiple stamps appear over redactions as a comma separated list.

Note

Redactions containing multiple stamps can be batch deleted via batch deletion of redactions by stamp. To fully delete a redaction by stamp, all stamps applied to the redaction must be selected for deletion. If only a subset of stamps is chosen, the redaction is retained with the remaining stamps, while the selected stamps are removed.

To learn more about applying redaction stamps, visit Redactions - Apply redaction stamps.

Create database usage notifications

Organization Admins can now configure forecasting notification rules for database usage thresholds. This offers Admins responsible for managing database usage an efficient, automated means to track what's coming in at the organization level. It is particularly beneficial for organizations operating across a high number of databases.

Database usage notification rules can be defined based on one more database(s) or individual database fields. Each rule can have one or more customizable currency or GB thresholds and may be set to monitor active, ECA, or suspended data based on peak billable size. When a threshold is hit, an email notification is sent to all Organization Admins.

Prior to this feature release, data usage monitoring was a fully manual process that involved exporting data from the Database Sizes page to a spreadsheet and reviewing said data in a tool like Excel. This manual workflow can now be deprecated in favor of database usage notifications.

To learn more, visit Database Usage Notifications.

Sort by database size on the Organization Admin Database Sizes page

We made a set of small updates to the Organization Home > Database Sizes page, as a means to improve management of large numbers of databases. Organization Admins now have the option to:

  • Sort the table on the Database Sizes by either Peak billable size or Current billable size. To do this select the sort buttons in the respective column header.
  • Filter the table by a minimum Peak billable size or a minimum Current billable size. To do this, select the filter button in the respective column header. Then, in the dialog that appears, enter a minimum value (e.g. 5) assuming the unit is GB.

    This filter is inclusive of that minimum value. For example, if you enter the number 5, the table will filter to show all rows with a value of 5GB or greater in the respective column.

Upload M365 Purview exports and review sets via cloud connection with Purview

With this release, you can upload Microsoft Purview exports directly into Everlaw through Everlaw's cloud connection with Microsoft Purview. An export is a review set that you have packaged and prepared for download within Purview. Previously, these exports had to be downloaded from Purview and uploaded to Everlaw through your local machine.

To learn more, visit Upload M365 Purview Exports via Cloud Connection with Purview

Access User Activity events using API

Organizations using Everlaw's API can now retrieve User Activity using the API. This new API functionality allows your organization to monitor Everlaw user activity and integrate that information into additional tools, like those used for cybersecurity monitoring. 

Information on user activity available through the API mirrors what is available in Everlaw, including user names, project names, and case-specific information like the names of codes. Specifically, you can now use the API to gather information on user activity from each of the following levels:

Access document information using Search API

Organizations using Everlaw's API for searches can now access document-level information for the results of their searches, which makes the results more actionable. The document-level information available for each document returned by the search is:

  • Bates/Control # 
  • Document ID
  • URL to open that document in the review window

Option to set the default time zone during native upload

Users performing a native upload can now choose whether or not to select a default time zone. Previously, this field was required and set to UTC, unless otherwise specified. Now, it can be left blank. You should leave the Default timezone blank if you do not know the time zone of the data you are uploading.

You can find this optional Default timezone field located in the Details step of a native upload, under Advanced settings > Language and location > Default timezone. 

Note

You can remove the default time zone from a pre-existing upload. To do this, reprocess your Everlaw processed document(s) with the Advanced settings > Default timezone field set to No timezone.

Set a transcript starting page in Storybuilder Depositions

Storybuilder users can now renumber the starting page and number of cover pages in Depositions. This is helpful when multiple days of testimony are spread out over multiple Depositions or if the transcript contains cover pages that do not contain actual testimony.

 

Renumbering pages of a Deposition transcript carries over to the transcript viewer page navigation and transcript citations.

Resize side navigation on the homepage

The side navigation of the homepage, where the filters, document overview, and folders, are displayed, is now resizable and can be made wider. To change the width of the side navigation:

  1. Hover your cursor over the line separating the side navigation from the rest of the homepage.
  2. Hold down the cursor, drag the line to the desired width, and release the cursor.

The selected width is not persistent. Each time you leave the homepage and come back, or when you refresh the page, the side navigation will be the default width. 

Fast follow-ups to Entity management release

We made three small updates related to the recently released entity management for Database Admins feature (released in January ‘25). They are as follows:

  • Database Admins can now search entities by email address on Database Settings > Entities page. Previously, they could only search by name.
  • The database's total number of entities and shared emails are listed on their respective tabs of the Entities page.
Before After
  • The Contact Names filter option in Data Visualizer is now called Entities. This is purely a label change, not a change in behavior.
Before After

Visual improvements

  • In Project Settings, Production tools is now in its own tab under the General tab. Production tools used to be a section within the General tab.
Before After
  • On the Organization Home > Database Sizes page, the Filter field is now labeled Filter by database. We also added a new Filter by field value, which allows you to filter by database field.
Before
After