Who might be interested:
Users who will be administering Everlaw across all databases owned by their organization. This training session is specifically tailored for users who will be administering all of their organization's cases on Everlaw under an annual contract and is only offered as a custom session.
What you will learn:
How to navigate the Organization Administration dashboard. How to create, rename, suspend, and delete databases owned by your organization. How to monitor activity across your organization.
Watch a short introductory video on organization administration permissions and abilities.
Attend a live, custom training on organization administration permissions and abilities with a US-based trainer.
Learn more about Administrator Permissions
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. They can also grant database permissions to other users (ability to upload or delete documents).
3. Project administrators control the project settings, which includes giving users access to projects, controlling their project permissions, creating codes and persistent highlights, and more.
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. 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. Read the ECA databases help article.
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. Read the database administration and permissions help article.
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. 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.