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 search grouping

In the general settings tab, you can configure the default search grouping. By default, new projects created on Everlaw (after Release 89) will have the default search grouping setting enabled and set to group by attachments without grouped non-hits.


When enabled, this will be the initial grouping settings for all users in the project creating a new search. Note that this grouping–by attachments without grouped non-hits–will order documents in the results table according to their attachment family and will not pull in associated documents that do not meet the search criteria.

If you would like to change the default, you can toggle off or toggle on the setting and select the desired grouping configuration.

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.


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.


Default binder sharing option

Project-wide default binder sharing can also be configured in the General tab in Project Settings. By default, new projects created in Everlaw (after the Jan 2024 release) will have the default binder sharing option enabled with the default recipient of the Administrator group with Edit permissions. Project admins may toggle on/off this setting and configure default recipients and permissions.

When enabled, project members creating a new binder will see the default recipient and permissions auto-populated but may choose to edit them or to not share for that binder. The project-wide binder sharing setting applies to new binders created from the homepage, in the batch coding panel, and in the review window coding panel. It does not affect existing binders that were created prior to configuring or changing the setting, and it does not apply to binders created during upload.

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). 


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


By default, the timezone is set to UTC. Timezone information will always be appended to datetime values displayed on the platform. If no timezone information was found for the datetime value, which can happen if a processed document was uploaded with no timezone information for that value in the load file, an (unknown timezone) marker will be appended instead.

Click the box to open a dropdown menu of timezone options. This setting affects how Everlaw metadata fields are displayed if they are datetime fields. 


In the example above, the original datetime field for the document had a time of 10:31 PM, UTC on March 20, 2017. After changing the project setting timezone from UTC to US/Pacific, the Everlaw metadata field is represented as 3:31 PM, Pacific on March 20, 2017.

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. 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.


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.


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. 


Persistent highlights

Visit this article for more information about persistent highlights.

Language tools

You can enable non-English language translation here. Translation can be set to Google Translate (the platform default), AWS Translate, or No translation (which will disable machine translation entirely). 


By default, Everlaw uses Google’s enterprise translation API for generating translations. Google does not permanently store any data in relation to its enterprise translation services. If you select Google Cloud Translate and you are an EU or UK customer, your translation data will be routed through the EU Endpoint instead of the global or US endpoint. For more about Google’s data confidentiality policies, please go to their FAQ, and scroll down to the “Data Confidentiality” section.  (Please note that this link will take you to an external website away from Everlaw’s Knowledge Base.)

You can also choose to set your project’s translation provider to Amazon Translate.  You can read more about Amazon’s  data confidentiality policies here under "Data Privacy." (Please note that this link will take you to an external website away from Everlaw’s Knowledge Base.) 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 our translation API. 

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


Article is closed for comments.