> ## Documentation Index > Fetch the complete documentation index at: https://support.legora.com/llms.txt > Use this file to discover all available pages before exploring further. # How do I enable the Word Add-in for users in my Legora org? > In this article, you’ll learn how to enable the Legora Word Add-in for users in your organization. You can deploy the add-in centrally as a Microsoft admin, or users can add it themselves if your organization allows user-managed add-ins. ⚠️ Choose the correct Word Add-in listing for your organization: * If your organization has migrated to Legora’s global authentication, install **Legora for Word (Global)** from Microsoft AppSource. * If your organization still uses a regional Legora instance, install the matching regional add-in. For example, if users access Legora at `app.eu.legora.com`, install **Legora (EU Processing)**. ## Prerequisites Before you begin: * Users must sign in to Word with their organizational Microsoft (Entra ID) account. * To use the add-in after installation, users need a Legora account with access to the relevant workspace. * For centralized deployment, you must have the right Microsoft admin permissions. * Use a supported version of Microsoft Word: Windows Word version 2311 or later, Mac Word version 16.79 or later, or Microsoft 365 Word on the web. ## Centralized deployment licensing Centralized deployment requires that users receiving the add-in are licensed with a Microsoft 365 or Office 365 suite that includes Exchange Online, and that they have an active Exchange Online mailbox. Supported suites include: * Microsoft 365 Business Basic, Standard, Premium * Office 365 E1, E3, E5 (and F3) * Microsoft 365 E3, E5 (and F3) Standalone **Microsoft 365 Apps for Business** or **Microsoft 365 Apps for Enterprise** does not include Exchange Online. Users on these plans alone cannot receive centrally deployed Office add-ins, including the Legora Word Add-in. Centralized deployment can be performed by: * **Global Administrator**: recommended, with full management capabilities * **Exchange Administrator**: can deploy and manage add-ins through the Microsoft admin center ## Choose the correct AppSource listing Install the listing that matches your organization’s Legora setup. **Regional listings** (for organizations that still use regional Legora environments): * [Legora (EU Processing)](https://appsource.microsoft.com/en-us/product/office/WA200007740?tab=Overview) * [Legora (US Processing)](https://appsource.microsoft.com/en-us/product/office/WA200008317?tab=Overview) * [Legora (AP Processing)](https://marketplace.microsoft.com/en-nz/product/office/WA200009163?tab=Overview) For Australia, use the AU manifest in [Word Add-in manifests](/word-add-in-manifests). It is not an AppSource listing. **Global listing** (for organizations that have migrated to Legora’s global authentication): * Search Microsoft AppSource for **Legora for Word (Global)** If you are unsure which listing to use, check with your Legora representative or review your organization’s authentication migration status. ## Enable the Word Add-in as an admin 1. Open the correct Legora Word Add-in listing in Microsoft AppSource. 2. Select **Get it now**. 3. Sign in with your Microsoft admin account. 4. On the **Deploy New App** screen, choose which users or groups should have access to the Legora Word Add-in. 5. Continue through the deployment steps. 6. Confirm that the app publisher is **Legora AB**. 7. Complete the deployment. You’ll know this worked when the Legora Add-in appears in the Word ribbon for the users assigned during deployment. After centralized deployment, it can take up to 24 hours for the add-in to appear for all assigned users. ## Add the Word Add-in as a user If your organization allows users to add Office add-ins directly, users can add the Legora Word Add-in themselves. Choose the listing that matches your organization’s Legora setup. ### Word Online 1. Open Microsoft Word Online. 2. Select **Add-ins** in the ribbon. 3. Search for **Legora**. 4. Select the correct Legora Add-in for your organization. 5. Add it to Word. ### Word Desktop #### **Through AppSource:** 1. Open the correct Legora Word Add-in listing in Microsoft AppSource. 2. Select **Get it now**. 3. Follow the prompts to open or add it in Microsoft Word. #### **Through Word:** 1. Open Microsoft Word on your desktop. 2. Go to **Home**. 3. Select **Add-ins** → **More Add-ins**. 4. Search for **Legora**. 5. Select the correct Legora Add-in for your organization and select **Add**. You’ll know this worked when the Legora Add-in appears in your Word ribbon. ## Troubleshooting ### If users cannot see the add-in If users cannot see the Word Add-in after centralized deployment: 1. Confirm that the users or groups were included in the deployment. 2. Confirm that users are signed in to Word with their organizational Microsoft account. 3. Allow time for Microsoft 365 changes to propagate. It can take up to 24 hours for a centrally deployed add-in to appear. 4. Ask users to close and reopen Word. 5. Ask users to refresh admin-managed add-ins: **Add-ins** → **More Add-ins** → **Admin Managed** → **Refresh**. 6. Check whether your Microsoft admin settings allow the add-in to appear in Word. 7. Contact your Microsoft admin or Legora support if the add-in still does not appear. For more troubleshooting steps, see **Word Add-in missing, not loading, or no longer available**. ### If the add-in appears in the wrong environment If your organization still uses a regional Legora environment (EU, US, AP, or AU), confirm that you installed the matching regional Word Add-in. For Australia, use the AU manifest in [Word Add-in manifests](/word-add-in-manifests). The add-in environment should match the Legora app environment your users access in the browser. If your organization has migrated to Legora’s global authentication, install **Legora for Word (Global)** instead of a regional listing. ## Frequently asked questions ### Does the Word Add-in support .MSI files? No. The Word Add-in is an Office web add-in. It is not distributed as an executable `.EXE` file or `.MSI` installer.