Requirements
Make sure your environment supports TermLynx.
Compatibility for TermLynx v5
Office 365 (Microsoft 365) is recommended. This table is the shared compatibility guidance for TermLynx v5; it describes requirements, not a certification of every Office build or browser version. Confirm your organization's specific configuration during your pilot.
| Client | Office / platform | Browser or embedded runtime |
|---|---|---|
| Word on Windows | Supported Windows and Word builds, Word 16.0.5317.1000 or later; Office 365 recommended. Volume-licensed Office must meet the same runtime requirement. | Microsoft Edge WebView2 required; installed with supported Office versions by default. |
| Word on Mac | Supported, up-to-date Word and macOS versions. | Safari's WKWebView, supplied by the platform. |
| Word on the web | Microsoft-supported Word web configuration. | A current browser supported by Word on the web. |
| TermLynx Viewer | Standalone web application; Word is not required. | Current Microsoft Edge (Chromium-based), Chrome, Firefox, Brave, or Safari. Windows WebView2 is not required. |
IE11 and EdgeHTML are not supported. See Microsoft's Office browser guidance for Office build and runtime details.
Microsoft Office
Windows
TermLynx requires Microsoft Word 16.0.5317.1000 or later on Windows, on a supported Office build that uses Microsoft Edge WebView2 for Office Add-ins. This minimum does not guarantee that every later build or Office edition uses WebView2; both the supported-build and runtime requirements apply. IE11 and EdgeHTML are not supported.
WebView2 is installed with supported versions of Office by default, including Microsoft 365 (Office 365). Keep Office and the WebView2 Runtime up to date.
If your organization uses volume-licensed Office instead of Office 365, the same WebView2 requirement applies. An older Office installation that uses IE11 or EdgeHTML must be updated or upgraded before using TermLynx. Installing the runtime alone does not make an unsupported Office version compatible.
See the WebView2 requirements below.
Office update
If you install Microsoft Word with Office 365, you can apply the updates from within Microsoft Word itself. No administration rights are required.
Step by step
- Open Microsoft Word with an empty document
- Go to File and then Account
- Under Product Information, choose Update Options and then Update Now
See the official documentation:
Windows update
An alternative to the built-in Office Update is to use Windows Update to apply the patches and activate the "other Microsoft products" option.
Step by step
- Click on the Windows key
- Search for Windows Updates
- Select the Windows Updates settings result
- Click on Advanced Options
- Turn on the switch Receive the updates for other Microsoft products when you update Windows
- Click on the back arrow at the upper left corner
- Click on Check for updates
Windows will now update and download all security and stability patches for Microsoft Office. You might need to restart your PC afterward.
Mac
Use supported, up-to-date Word and macOS versions with Office web-add-in support. Office Add-ins on Mac use Safari's WKWebView; the Windows WebView2 requirement does not apply. Validate the specific Word/macOS combination and required Office.js APIs during your pilot, including document upload and supported paragraph-change notifications. A precise tested Mac minimum has not yet been published; this guidance does not cover all historical Office editions.
If you experience issues, you can try to update using the official documentation.
Web Add-ins
By default, Microsoft Word enables web add-ins. Many IT departments have group policies or registry configurations that turn them off and prevent end-users from arbitrarily installing web add-ins listed on the store.
If web add-ins are turned off, the Insert Add-in button will be disabled in Microsoft Word. You won't be able to install TermLynx in Microsoft Word.
Enabling web add-ins
Ask your administrator to disable or leave unconfigured the Block Web Add-ins policy. Enabling this blocking policy prevents web add-ins from running and overrides the other Trusted Catalogs policies.
The user policy uses HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\WEF\TrustedCatalogs, value disableallcatalogs: 1 blocks web add-ins; 0 disables the blocking policy. When the policy is unconfigured, other Trusted Catalogs policies still determine which sources are allowed. Have your administrator check effective Group Policy rather than relying on a local registry edit that may be overwritten.
Disabling the store
The Block the Office Store policy controls whether users can use or insert add-ins from the Office Store. It uses the same user registry key as above, with value disableomexcatalogs: 1 blocks store add-ins; 0 disables this blocking policy. Disabled or unconfigured permits store add-ins only if other policies do not block web add-ins.
For centrally managed deployments, have your administrator validate the effective policies with centralized deployment before rolling them out. Do not enable this blocking policy for TLZInstaller: its store command requires the store policy to permit access even when store controls are hidden. See TLZInstaller policy guidance.
WebView2
WebView2 is required for TermLynx in Microsoft Word on Windows. It is not an optional performance upgrade. IE11 and EdgeHTML are not supported.
WebView2 embeds the Chromium-based Microsoft Edge engine in desktop applications. Microsoft installs the WebView2 Runtime with supported versions of Office by default, so a separate installation is normally unnecessary.
This requirement is specific to Windows desktop Word. Word on Mac uses Safari's WKWebView. Word on the web uses the browser in which it is opened; use a current browser, not IE11 or EdgeHTML.
Microsoft guidance
See Microsoft's requirements for using WebView2.
If WebView2 is missing or Word is not using it
- Update Office and confirm that your Office edition is still supported, using Microsoft's guidance above. Ask your IT administrator to upgrade unsupported installations.
- Check Windows Installed apps or Apps & features for Microsoft Edge WebView2 Runtime.
- If the runtime is missing, ask your IT administrator to install it from Microsoft's WebView2 download page.
- Restart Word. If the add-in still cannot start, ask your IT administrator to check the Office installation and policies.
Installing WebView2 does not enable TermLynx to run in IE11 or EdgeHTML, and it does not bypass Office compatibility requirements.
Firewall
Third-party services
TermLynx uses third-party services for Office integration and, depending on deployment configuration and usage, diagnostics and billing. The visible sign-in flow uses emailed authentication codes, not social sign-in.
Allowlist
If your organization restricts outbound connections, use the following as a starting point for administrator validation, not a complete, owner-verified production inventory. Client destinations use HTTPS (TCP port 443). Validate the complete list against a representative production deployment, including redirects and dependent resources; manifest navigation permissions are not a network inventory.
| Destination | Purpose | Direction | Requirement | Environment / validation |
|---|---|---|---|---|
| https://webaddin.termlynx.com | TermLynx application and document uploads | Client → service | Required | Public production service; confirm the hostname for other environments. |
| https://appsforoffice.microsoft.com | Office.js, loaded from /lib/1/hosted/office.js | Word client → Microsoft CDN | Required for Word integration | Referenced by the application; include in deployment testing. |
| https://o258073.ingest.sentry.io | Diagnostics and crash reporting | Client/server → configured Sentry service, where enabled | Conditional; not a universal client requirement | Operations must confirm enabled integrations and current endpoint(s); do not assume a historical ingestion hostname is current. |
| https://billing.stripe.com, https://checkout.stripe.com, https://invoice.stripe.com, https://m.stripe.com, https://js.stripe.com | Billing | Billing user's browser → Stripe | Required only for individual licenses; not required for enterprise licenses | Confirm destinations from the actual production invoice/billing flow before allowing them. |
Review Microsoft 365 URLs and IP address ranges for current Office service network requirements and Microsoft's Office Add-in troubleshooting guidance for add-in connectivity issues. Office installation, deployment, and host services may need additional Microsoft endpoints.
Server-side egress is a separate operational inventory, including configured authentication and other backend providers. Those service-to-service destinations should not automatically be added to every client allowlist. Operations must validate them for the deployed environment.
Automated emails
Users must receive authentication codes to sign in, not just to activate an account. Enter your email, select Send code, then enter the emailed code and select Submit. See passwordless sign-in.
Security scans and Junk-folder filtering can delay delivery, interrupt training, and reduce adoption. Check spam or junk folders and use Resend; contact your administrator if no code arrives after 5 minutes.
Before deployment, operations should verify the current provider configuration and inspect delivered message headers to identify the actual From address/domain and Return-Path domain. Use those verified values to prepare precise filtering guidance with your mail administrator; do not rely on an unverified historical sender or envelope domain, or bypass mail security checks broadly.
LLM endpoint (optional)
An LLM endpoint is required to enable certain definition generation features and confidential information scrubbing. This is optional for using TermLynx; without a configured LLM provider, these features remain disabled.
- Organizations: Provide your organization's custom LLM endpoint and an access token.
- Users with an individual TermLynx subscription: You may use the global OpenAI API endpoint with an OpenAI API token.