Enable Everlaw for Word (Admin & IT)

Everlaw for Word is a Microsoft Word add-in (plugin) that brings your team’s Story's evidence into the Word documents you are drafting. The add-in allows users to cite evidence in Word without switching back and forth between Everlaw and their document to find cited evidence. 

With the add-in, they can open any Word document that contains Bates citations in the add-in, and those citations link back to the right version of each document, stored securely in Everlaw with all your team's work product for that evidence.

This article covers how to enable your team to use Everlaw for Word.

Requirements

• An Organization Admin must enable OAuth access for your organization before anyone can sign in to the add-in.
• If your IT department has turned off self-installation of Office add-ins, you will need them to deploy the Everlaw for Word add-in centrally
• The add-in runs in Word on Windows, Word on Mac, and Word on the web. Users will need Word Online, a Microsoft 365 account, or perpetual Office 2024 or later.
• Users need an internet connection. Evidence details are served from Everlaw and are not stored in the Word document.

Get your team started

1. Enable OAuth access for your organization: Everlaw for Word signs users in through Everlaw's OAuth flow, so API access must be enabled before anyone in the organization can use the add-in. Until this is done, users can install the add-in but cannot sign in.
   This is a one-time organization-level setting. It applies to every user and every project in the organization.
   To enable OAuth access:
   1. From Organization home, go to Organization settings > API Access.
   2. In the OAuth2 section, select Enable API access via OAuth.

2. Confirm user permissions: Users must have Receive, Create, or Admin permission for Storybuilder in the project they want to work in. 
3. Check if you need IT support: If your IT department has turned off self-installation of Office add-ins, you will need them to deploy the Everlaw for Word add-in centrally. You can determine if this is the case by asking your IT directly or by attempting to install the add-in yourself.
4. Enable them: To get your team up and running, point them to our Everlaw for Word article, where they can learn how to install the add-in in their own Word environment and how to use it in tandem with Everlaw.

Deploy the Word add-in centrally

Some IT departments turn off self-installation of Office add-ins, in which case Everlaw for Word does not appear in the Microsoft Add-ins menu. Your Microsoft 365 administrator can still make the add-in available by deploying it centrally from a manifest file.

An Office add-in consists of a small XML manifest file plus the web application it points to. The manifest tells Word the add-in's name, where its button belongs on the ribbon, and which web address to load, so deploying the manifest gives users the add-in without them installing anything themselves.

Before you start: Download Everlaw for Word’s manifest file

To deploy the add-in:

1. In the Microsoft 365 admin center, go to Settings > Integrated apps, then select Upload custom apps.
2. Select Office Add-in as the app type, then upload the manifest file Everlaw provided.
3. Assign the add-in to the users or groups who need it, then finish the deployment.

The add-in can take up to 24 hours to appear for assigned users. It then appears on the Home tab automatically, and users sign in as described above.