You can now connect directly to your Everlaw projects from within Legora. This means that you can securely bring in your Everlaw evidence layer when you use Legora for analysis and drafting.
In this article we'll cover:
- Everlaw functionality available from within Legora
- Guidance for connecting Everlaw with Legora
Requirements
Pre-requisite: Before any user can connect to Everlaw from within Legora, an Everlaw Organization Admin must switch on the OAuth2 setting within Everlaw. Once it's switched on, the connection to Legora can be enabled.
To leverage Everlaw from within Legora, you must have the following:
- A Legora account within a Legora organization that has enabled the Everlaw integration
- An Everlaw account with access to at least one project: The searches and evidence you have access to within Legora are limited to the Everlaw project(s) and documents you have access to.
Note
At this time, this connection is not available to our users in our GovCloud environment.
Data privacy and security
Your data privacy and security is our priority. Your use of Everlaw and our data privacy and security commitments to you are governed by our Terms of Service and Data Processing Addendum.
Your interactions within your Legora environment are governed by your specific customer agreement with Legora, which also outlines their security and data privacy practices.
Note
The connection between Everlaw and Legora is read-only, meaning that you cannot make any changes to, export, or delete documents from within Legora.
Enabled functionality
Within Legora, you can write queries in natural language. Legora will translate them into Everlaw syntax and return the results. The following types of searches are currently enabled by the Legora connection:
- List the projects you have access to within Everlaw
- Deep Dive questions (for Everlaw projects with Deep Dive enabled)
- Direct lookup by Bates/Control #
- Query document text
- Combine text queries with a filter based on custodian and/or date range
- Metadata is accessible for retrieved documents, but cannot be queried directly
Connect Legora to Everlaw
Connecting Everlaw to Legora happens in three steps.
Step 1: Everlaw Organization Admin Enables OAuth2
This step must be done by an Everlaw Organization Admin. Instructions for how to do so are in the Organization Admin: Everlaw API article.
Step 2: A Legora Admin enables the Everlaw integration
A Legora administrator must make the Everlaw integration available from within Legora.
Read more about Legora integrations in Legora's Self-service integrations: Overview article.
Step 3: A user authenticates their Everlaw credentials
Requirements
To connect Legora to Everlaw:
- Your Legora admin must have added the Everlaw integration from within Legora
- You must have access to at least one Everlaw project
To connect to Everlaw, go to Settings > Connectors. On the Everlaw connector, select Connect.
You will be prompted to authorize the connection and sign into your Everlaw account.
For users on projects in multiple organizations
Legora's ability to search Everlaw projects is based on the owning organization's enablement of OAuth2 in Everlaw. If you have access to projects owned by multiple organizations, you will only be able to use Legora to search the projects for which OAuth2 has been enabled at the Organization level.
You only need to follow the steps to form the connection within Legora once. When an additional organization enables Legora, the projects within that organization that you have access to will immediately become searchable within Legora.