There are three different levels of administration on Everlaw:
1. Organization administrators are on an annual contract and have special access to certain features.
2. Database administrators have the ability to upload and delete documents in a database. They can also create projects and request deletion of a database.
3. Project administrators control the project settings, the workspace where review work is performed and a case is built.
Depending on your level of permissions, you may have access to some or all of these tools. You can learn about each of these roles below.
Organization administrator access is the highest level of permissions a user can have on Everlaw. These organization administration tools are only available to clients using Everlaw on an annual contract. In addition to the videos below, check out these organization administrator help articles to get started:
Clicking on the diamond "A" will give you access to your organization's dashboard where you can see all projects owned by your organization, user activity, and more.
Watch the 10 minute video, or
Read the dashboard tabs help article
ECA databases comprise of at least two projects, an ECA project and a Review project. From the ECA project with limited functionality, you can identify and promote documents for full review in the Review project. Data stored only in the ECA project will be billed at a lower rate.
Watch the 7-minute video, or
Read the ECA databases help article
Topics covered include:
Navigating the organization administration dashboard
Creating, renaming, suspending, and deleting a database
Managing users and monitoring activity across your organization
A database is the central storage location for all documents in your matter. It contains the clean versions of all your uploaded documents, which are then made available for review in projects. Database permissions grant individual users the ability to perform actions that affect all projects in a database.
Uploading and deleting documents affect which documents are in your matter's database. This is why upload and delete permissions are categorized under database permissions.
Watch the 3 minute video, or
Projects under one database allow you to create new review environments using the same underlying set of documents. Review product is not shared between projects. They are useful for multi-firm matters, or cases that have expert reviewers or consultants.
Watch the 6 minute video, or
Read the projects help article
While database permissions allow you to change your database, project permissions grant access to features and tools within individual projects. These tools include codes, assignment groups, and predictive coding models. Generally, actions made permissible by project permissions do not affect other projects in the database. For more information on the difference between database and project permissions, read the database and project permissions help article or the database vs. project downloadable guide.