General Settings

Table of Contents

By clicking the General tab in Project Settings, you will be taken to a variety of settings that you can configure.

Multifactor authentication

In the general settings tab, you can enable multifactor authentication for the project. Every user who is added to that project will be required to use MFA (via a one-time email code) when logging in.  

Production tools

Production tools include a code wizard with preset production codes, as well as settings for redaction stamping. You can learn more about production tools in this help article 

Default assignment review criteria

Assignment review criteria are the conditions that documents must meet to be considered reviewed. This setting establishes the default review criteria for assignment groups.

When you create a new assignment group, it will use these review criteria by default. For a particular assignment group, you can change the review criteria to something other than the default when you create an assignment group, or when you update an assignment group via the assignment group admin dashboard.

When you update the project-wide default here, all assignment groups currently using the default review criteria will have their review criteria updated to this new default. However, changing the default here will not update any assignment groups that already have custom review criteria.

To set or change the default assignment review criteria, navigate to the General tab in the Project Settings page. Click the “Review criteria” button. The default review criteria is “any rating," meaning if a document is rated, it is considered reviewed.

Screen_Shot_2020-01-09_at_2.08.41_PM.png

A query builder will pop up where you can add your desired combination of labels. Just like on the search page, you can negate a term by clicking on it, switch the logical operator by double clicking, and nest logical operators within each other.

edit-criteria-r64.png

Homepage view

By default, new users will see the card view of the homepage when they first log in. This setting allows you to set the document overview as the default homepage for new users. Note that this setting only applies to new users logging in for the first time. For existing users, the homepage will default to the last used view. 

Full screen review

By default, all new databases will default to the full screen mode in the review window. If you would like to change the default view from full screen to the classic review window, toggle this setting from green to grey (on to off). 

Screen_Shot_2019-02-28_at_11.00.34_AM.png

Note that new projects you create in the database will not reflect any changes you've made to the default. 

Timezone

By default, the timezone is set to UTC. Click the box to open a dropdown menu of timezone options. This setting affects how Everlaw metadata fields are displayed if they are date/time fields. For example, the Dates field represented in the metadata table of the review window will be adjusted to the timezone you specify. 

Screen_Shot_2020-01-09_at_2.23.01_PM.png

The date/time Everlaw metadata fields will be adjusted. In the example above, the original date/time field had a time of 7:23 AM, Pacific. After changing the project setting timezone to EST, the Everlaw metadata field is represented as 10:23 AM, Eastern.

Date and Time Format

You can choose how you would like your date and time metadata to display across your Everlaw project. For example, you may want your Date field to show up as dd/mm/yyyy instead of mm/dd/yyyy. By default, the date and time format is set to the regional norm according to your VPC. To adjust your date or time format, click the date or time field to open a dropdown menu of display options. This setting affects how Everlaw date/time metadata fields, Story dates/times, and freeform codes with the DateTime format are displayed. Date and time selectors will also be updated to reflect your date and time settings.

Screen_Shot_2020-12-14_at_10.53.56_AM.png

Page Size

This setting affects the size of PDFs generated when Everlaw processes native documents. By default, the setting will match the region of the instance of your project. Everlaw will generate PDFs in the selected size for documents that do not have a described size (e.g. emails). Documents with an explicit size (e.g. PDFs, word documents, and images) will remain in their original sizes. Documents exported, printed or produced from Everlaw will respect the size of the pages on the platform.  

Additional Tabs

In addition to the general settings, a dropdown will appear below the General tab that allows you to configure three more settings for the project: stories, persistent highlights, and language tools.

Note that new projects you create in the database will not reflect any changes you've made to the default.

Stories

By default, each project on Everlaw has one Story. You can add more Stories to your project here by clicking "New Story." We recommend only having one Story on your project.

You can also hide a Story by clicking the associated eye icon. This will hide all associated work product, including its Drafts and Depositions, for all users on your project. You must have at least one Story visible at all times.

Note: changes to visibility will not be enacted until the user refreshes the page. Additionally, some previous actions (like creating searches) associated with hidden Stories will still be available. 

Screen_Shot_2020-01-09_at_2.09.46_PM.png

Persistent highlights

Visit this article for more information about persistent highlights.

Language tools

You can enable foreign language translation here. By default, machine translation is disabled. You can click on the toggle labeled "Enable translation" to turn it on. 

language_tools.gif

Everlaw's primary commercial environment uses Google’s enterprise translation API for generating translations. Google does not permanently store any data in relation to its enterprise translation services. For more about Google’s data confidentiality policies, please go to their FAQ, and scroll down to the “Data Confidentiality” section.

Some VPCs run through Amazon Translate. You can read more about their data confidentiality policies here under "Data Privacy." Please note that Everlaw has opted out of having user translation data used to develop Translate and other AWS AI tools.

In order to search for non-English languages in Everlaw, you must add the language in Language Tools. Type the name of one of the supported languages into the bar underneath “Expected Languages.” This will populate the “Language” search term with your expected languages and allow the system to search for documents in those languages.

Everlaw's translation search capability performs best with documents that contain long sections of contiguous text that are in the same language. For example, if you have a document that is nearly completely in English with a handful of Spanish words interspersed throughout, the system will have a more difficult time picking up on the non-English content than if the document had entire paragraphs in Spanish.

Everlaw can translate any language supported by Google or AWS Translate, depending on which service is being used. 

Everlaw can detect the following languages:

  • Afrikaans
  • Albanian
  • Arabic
  • Bengali
  • Bulgarian
  • Chinese (simplified)
  • Chinese (traditional)
  • Croatian
  • Czech
  • Danish
  • Dutch
  • English
  • Estonian
  • Finnish
  • French
  • German
  • Greek
  • Gujarati
  • Hebrew
  • Hindi
  • Hungarian
  • Indonesian
  • Italian
  • Japanese
  • Kannada
  • Korean
  • Latvian
  • Lithuanian
  • Macedonian
  • Malayalam
  • Marathi
  • Nepali
  • Norwegian
  • Persian
  • Polish
  • Portuguese
  • Punjabi
  • Romanian
  • Russian
  • Slovak
  • Slovenian
  • Somali
  • Spanish
  • Swahili
  • Swedish
  • Tagalog
  • Tamil
  • Telugu
  • Thai
  • Turkish
  • Ukrainian
  • Urdu
  • Vietnamese
Have more questions? Submit a request

0 Comments

Article is closed for comments.