DOCSEARCHbyAlgolia
Submit Docs

TermLynx Documentation

website·Indexed 31 days ago

https://docs.termlynx.com/

Documentation for TermLynx, including installation and deployment guides for the Microsoft Word add-in via TLZInstaller, centralized deployment, and the add-in store. Covers system requirements such as WebView2, firewall configurations, and web add-in enablement, as well as user management, pilot guidelines, and legal policies regarding data security and privacy.

Tokens
9.7K
Snippets
11
Records
79
Agent score
45%

What's inside TermLynx

  1. Best practices for selecting TermLynx pilot participants

    To maximize the success of a pilot, consider the following criteria when selecting participants:

    • Tech-Optimism: Select users excited about productivity tools; avoid those uninterested in new technology.
    • Role Alignment: Participants must be individuals who draft or review English-language legal agreements in Microsoft Word.
    • Experience Level: Organizations typically find more success onboarding younger lawyers (1-5 years experience) and those in a culture open to technology.
    • Timing: Avoid onboarding during high-stress periods (e.g., during a closing). The ideal time for training is immediately before they begin drafting a legal agreement.

  2. Understand TermLynx Data Security Scope and Monitoring

    The TermLynx Data Security Policy applies to all employees, contractors, consultants, guests, and affiliates accessing 'information resources' (data, hardware, software, and networks). This includes privately owned devices (laptops, smartphones, USBs) when used to access TermLynx resources.

    Users should have no expectation of privacy when using these resources. TermLynx may monitor activity, including login sessions, communications, and stored data, without notice if it is necessary to protect system integrity, respond to complaints, investigate unusual activity, or as required by law.

  3. Adhere to the TermLynx Cloud First Strategy

    TermLynx utilizes Linode for development and deployment. When initiating new IT investments, projects, or strategies, cloud services must be evaluated as the primary delivery option and adopted if they are the most effective way to meet business needs while complying with privacy and security standards.

  4. TermLynx Disaster Recovery and Business Continuity Overview

    TermLynx maintains a Disaster Recovery and Business Continuity Plan (BCP Program) to ensure information system uptime, data integrity, and availability during significant business disruptions. The plan is updated and tested at least annually on January 1st. Key infrastructure providers include Linode and Microsoft Azure.

  5. Understand TermLynx Software licensing terms

    The TermLynx Software is provided under a non-exclusive, non-transferable, non-sublicensable, and fully revocable worldwide license. The license is granted for the duration of the Subscription Term and is limited to the internal business purposes of the Customer. Usage is restricted to the number of 'Seats' (unique logons with unique license keys) specified in the applicable Order Form. Acceptance of these terms occurs upon purchasing, downloading, installing, using, or clicking 'Accept' for the software.

  6. Side-load the TermLynx web add-in in Microsoft Word

    Side-loading allows you to install the TermLynx web add-in without using the Microsoft Store. This method is deprecated and only works on Windows clients. It requires hosting the manifest.xml file on a network share (a local folder cannot be used) and configuring that share as a trusted catalog in Microsoft Word.

  7. Install the TermLynx add-in from a trusted catalog

    Once the trusted catalog is configured, load the add-in into Word:

    1. Open an empty document in Microsoft Word.
    2. In the Insert ribbon, click My Add-ins.
    3. Select FILE SHARE.
    4. Click Refresh in the upper right corner.
    5. Select TermLynx and click Add.

    Note: If the 'Insert' button is disabled, ensure Web Add-ins are enabled in your Word settings.

  8. Secure software development and deployment at TermLynx

    TermLynx mandates specific security protocols for software development and deployment:

    • Code Storage: All software code must be stored in a Git repository hosted on Microsoft Azure DevOps.
    • Access Control: Git repositories must be accessed via SSH using a password-protected RSA 2048 encrypted key. These keys must not be stored in a digital safe; they must be memorized or stored physically under lock and key.
    • Secret Management: All deployment secrets must be stored exclusively on Microsoft Azure DevOps.
    • Communication: All SAS programs or applications must use HTTPS/SSL TLS for all communications with API clients.
    • Code Signing: Any software available for download on a client's device must be signed with TermLynx's designated code signed EV certificate signature.

  9. TermLynx system requirements and compatibility

    TermLynx is compatible with the following environments:

    • Desktop: Microsoft Word 2016+ on Windows 7-10 and Microsoft Word on Mac.
    • Web: Microsoft Word web client (operates within a restricted iframe).
    • Standalone Viewer: Accessible via web browser at https://webaddin.termlynx.com. Supported browsers include IE11, Edge HTML, Edge (Chromium), Chrome, Firefox, Brave, and Safari.

  10. Steps to deploy TLZInstaller

    To deploy the TermLynx Zero Installer, follow these steps:

    1. Download TLZInstaller.exe from TermLynx and place it on a file share.
    2. Run the TLZInstaller.exe as an administrator.
    3. Restart Microsoft Word and verify that the "Activate" button is present in the UI.

  11. Secure passwords using approved digital safes

    All users, including contractors and vendors, must use a digital password safe approved by the Chief Technology Officer (e.g., Dashlane) to generate and store passwords. This applies to all account types, including user-level, system-level, web, email, screen savers, voicemail, and local router logins. The password safe must be encrypted with a unique master password.

  12. Implement TermLynx device and workspace security measures

    To prevent physical and digital breaches, personnel must follow these security protocols:

    • Clear Workspace/Screen: Log out or activate a password-protected screensaver immediately when leaving a desk. Clear all sensitive documents, keys, and fobs from the workspace at the end of the day. Clear whiteboards after meetings.
    • Multi-Factor Authentication (MFA): Mandatory one-time enrollment for all information resources, specifically for Microsoft accounts and the digital safe. Use only approved Microsoft or Google authenticators.
    • Software & Updates: Only install applications with independently validated code sign certificates (others require CTO approval). OS security patches must be applied as soon as they are generally available.
    • Encryption & Storage: Store recovery keys and authentication keys only in the approved digital safe (e.g., Dashlane). Use encrypted tunnels (SCP, SFTP, SSH, HTTPS) or encrypted email for sensitive file transfers; USB drives are generally prohibited.
    • Network Access: Use a TermLynx approved VPN when accessing resources from public or unfamiliar networks.