March 1, 2024 Release: Import and export People in Storybuilder, redaction improvements, and more!

Expected AU release: February 27, 2024

Expected release for all other: March 1, 2024

Expected Knowledge Base updates: March 1, 2024

With this release, you can now import and export People in Storybuilder, add and export redaction information from the results table, 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 AI Beta updates: For Beta users only

Batch generate coding suggestions

Coding suggestions allow you to receive AI-generated evaluations of documents against user-provided coding criteria. With this release you can now easily generate coding suggestions across large batches of documents and view suggestions in the results table. 

You can also search on suggested codes, making it easier and more efficient to surface important documents and categorize sets of documents at scale. We will be updating this search term to support more fine-grained searching against suggested codes in a subsequent release. 

Learn more about coding suggestions here

Feedback on output

You can now give feedback on AI output directly from within the platform by clicking the thumbs up or thumbs down buttons.  You can also leave freeform feedback. This feedback is voluntary and used by Everlaw to improve our services. 

Learn more about our current beta feature set here

Import and export People in Storybuilder

In Storybuilder, you can now import and export People from a Story!

To import, navigate to the People page in your Story and select the “ + New Person” button on the upper left corner. This opens a New person dialog that will allow you to add people profiles through a CSV import. A CSV template is available for you to download to ensure proper formatting. 

To export, navigate to the People page in your Story. At the bottom of the People dialog is an option to export. You can rename your export, as well as choose which people to be included. By default, all people are selected. 

 Learn more about importing and exporting People in Storybuilder here.

Redaction improvements 

Add and export redaction information from results table

You can now add “Redaction Stamps” and “Redaction Stamp Details” columns to the results table. The “Redaction Stamps” column displays all unique redaction stamps applied on the document and its metadata. The “Redaction Stamps Details” column displays the page locations of redaction stamps. 

You can also now include the “Redaction Stamps” and “Redaction Stamp Details” fields in CSV exports production loadfiles, and privilege logs. 

Learn more about Redactions on Everlaw here.

Show recently used stamps

You can now see your recently used stamps when selecting redaction stamps in the review window or when creating batch redactions. The “recently used" section shows up to 3 recently used stamps if there are a total of 10 or more available stamps.

Default redaction stamp options

You can now change the default redaction stamp applied in the review window. Access the default redaction stamp settings  by clicking on the dropdown caret on the redaction tool.

There are 3 options available:

  1. No stamp: This is the current default. New redactions have no stamp applied by default.
  2. Redaction stamp: Choose a redaction stamp to apply to new redactions created on the review window using the redaction tool.
  3. Last applied redaction stamp: The last applied stamp is applied. For example, if you make a redaction with stamp A, then make a new redaction, this new redaction will have stamp A as well. If you then change any redaction to stamp B, the next new redaction will have stamp B.

Note that the default redaction stamp setting on hit highlights, as well as batch redactions, will stay as “No stamp” regardless of default redaction stamp settings.

Show redaction creation and edit history

The most recent redaction history is now displayed when you view redactions in the review window. If you don’t edit the redaction after you create it, your name and the time that you created the redaction is shown. If a redaction is edited by changing the size/stamp/partial redaction settings or adding/editing notes on the redaction, the timestamp is updated to show the user and time of the last edit. You need document history permissions and at least view permissions on redactions to be able to see these timestamps.

Media redaction creation/edit info is now shown in an info tooltip on the redaction.


Note that redactions edited prior to this release do not contain information about the user who last edited the redaction, but instead have a timestamp of the most recent redaction.

As before, you can view detailed redaction history from the document history tab of the review window for the history of all review work, including redactions made on a document.

Improved spreadsheet redaction

Users will now be able to redact spreadsheets up to 60MB in size.

Learn more about redaction stamps here.

Update to exported OPT files

We have updated how we generate OPT files to better support uploading data to Everlaw. Previously, exports that contained multi-page PDFs represented each document as a single line in the OPT file, regardless of the document's page count. With this release, we now add each page of a PDF as its own line in the OPT file. This improvement will give you the ability to upload data with OPT files generated by Everlaw. Note that this change does not affect the processed uploader, and the processed uploader still only accepts OPT files that contain one page per line.

Learn more about uploading processed data to Everlaw here.

Support editable metadata when importing work product

Currently, when exporting documents, you can choose to include “Review work product” in your export. This CSV can then be imported on the Codes panel of the Project Settings page.

We have updated the work product importer to support exports that contain editable metadata. When importing editable metadata fields, you can now create new metadata fields if they do not already exist. If you import editable metadata fields to an already existing field, the existing field is made editable.

Editable metadata fields are already included in existing work product exports, and exports done prior to this release can now be imported via the Projects Settings page.

Learn more about editable metadata fields here.  

Current billable size card on Project Size page

In addition to the existing “Peak billable size” and “Current total size” cards, we now display a “Current billable size” card on the Project Size page. This card reflects the billable size of the database, based on the existing (as opposed to peak) data volumes eligible for billing. It is useful for gauging the starting billable size for the next month. 

Learn more about the Project Size page here.

Native data upload improvements

Improved imaging of presentations with speaker notes

With this release, we are improving the legibility of presentations containing speaker notes. Previously, the PDF file created by Everlaw preserved the presentation's notes page orientation, which by default is portrait, as shown below. 

Now, the slide is larger, the PDF pages labeled with the slide number, and the orientation of the page matches the orientation of the slide:

As before, presentations with no speaker notes remain full-page, and long notes with overflow text continue on the page immediately following the slide. Overflow pages are now clearly labeled with the corresponding slide number. For example, if the slide above had a longer speaker note, the next PDF page would be labeled “Slide 2” since the note overflowing onto the page is for Slide 2.

We have also added the option to exclude speaker notes from the PDF file during native upload and reprocessing. Under Advanced settings Image details, select the option to exclude speaker notes from the PDF and text files created by Everlaw, with the slides in full-page for the PDF.

Learn more about uploading native data to Everlaw here

Update to Microsoft Teams data processing

During upload and processing of Purview format Teams chat data, Everlaw will now attempt to attach files by URL if SharePoint IDs are not present for these attachments. Purview exports do not consistently contain the SharePoint IDs to link attachments; this change allows Everlaw to more consistently link attachments to their respective chats.  Files attached this way will have a disclaimer indicating how they were attached. 

Learn more about uploading Microsoft Teams data to Everlaw here

[Organization Administration] Add database fields to the database sizes export

Organization admins can now export database fields alongside database sizes to more easily track and manage usage data across different types of matters in their organization. Once database fields are created, organization admins can filter on them in the Database Sizes table and include them in the CSV export of database or project sizes. From the Database Sizes table’s default view, organization admins can select to export database or project sizes and choose which fields to include as columns in their export.

When you view the Database Sizes table by database field, the CSV export reflects the filtered table, with each field value as a row.

Learn more about database fields here.

Upload from deactivated Slack custodians using the cloud connector

You can now select to upload from deactivated Slack custodians during the Custodian selection step of the Slack cloud connector. Deactivated Slack custodians are distinctly marked in the table with their Slack username followed by (Deactivated user). 

If you’d like to update the custodian’s name and/or remove the (Deactivated user) indicator, you can update their Everlaw display name in the native upload Custodians step.  

Learn more about uploading documents from Slack. 

Have more questions? Submit a request


Article is closed for comments.