The Word add-in.

/ 01What the add-in does

The add-in is a task pane that ships with five tabs.

• Analysis — the issue list with severity filters and glass-box toggle; "Apply All as Tracked Changes" inserts every suggestion as a w:del + w:ins pair
• Obligations — the extracted obligation matrix from Pass 2 Semantic, scrollable alongside the document
• Counterparty — Drafter / Reviewer mode toggle (enterprise tier only)
• Sentinel — regulatory gap scanner, vagueness scorer, renewal detection
• Settings — engine URL, jurisdiction default, tier, MFA status

It loads from apps/word-addin/ over HTTPS; nothing is bundled into the Word executable, so updating the add-in only requires updating the served HTML.

/ 02Deploying via 365 admin

Two paths: centralised deployment through the Microsoft 365 admin centre, or sideload for individual machines (testing only).

Centralised deployment

1. Obtain the manifest

   Download manifest.xml from the Parelion admin panel. The manifest is signed; do not modify.

2. Upload to 365 admin

   Settings → Integrated apps → Get apps → Upload custom apps. Choose Office add-in, then Upload manifest file.

3. Assign

   Assign to Specific users / groups (recommended) or Everyone. Group assignment respects nested groups.

4. Verify

   Allow up to 12 hours for propagation. The add-in appears under Home → Add-ins in Word.

/ 03SSO & engine URL

The add-in supports two auth modes. The default — SSO via the user's existing 365 identity — issues a JWT to the engine on first call. The fallback — API key — is provided for air-gapped deployments.

Engine URL

Set per tenant in the manifest's WebApplicationInfo resource element:

<WebApplicationInfo>
  <Id>11111111-2222-3333-4444-555555555555</Id>
  <Resource>api://engine.tenant.parelion.com/redline</Resource>
  <Scopes>
    <Scope>analyse</Scope>
    <Scope>export</Scope>
  </Scopes>
</WebApplicationInfo>

/ 04First run

On first open the add-in performs three checks in sequence and shows the user a single-line status:

• Engine reachable — TLS handshake to /health; green dot, latency in ms
• SSO valid — request /auth/sso/exchange with the Office identity token, receive a Redline JWT
• Licence — the JWT contains the tier; mismatch shows an amber banner with the upgrade path

/ 05Office.js manifest reference

The manifest is XML and follows the OfficeApp schema v1.1. The elements you will most often change: