> ## Documentation Index
> Fetch the complete documentation index at: https://docs.telepatia.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Manifest V3 Installation

> Institutional deployment guide for the Scribe Web Companion — MV3 build (Chrome, Edge, Chromium >= 88)

<Info>
  **Audience:** Hospital IT and Information Security teams.
  This guide covers the **Manifest V3** build — the recommended build for Google Chrome, Microsoft Edge, and Chromium forks with version >= 88.
</Info>

## Extension ID

```
fobdkddljbpmhnlclknlgcgbeeeojcnb
```

This is the 32-character identifier derived from the MV3 build's public signing key. Use this ID in all policy configurations below.

## Prerequisites

Before starting, complete the [environment assessment checklist](/scribe-web-companion/installation#institutional-deployment) and confirm:

* Workstations run **Google Chrome**, **Microsoft Edge**, or a Chromium fork with version **>= 88**
* HTTPS outbound connectivity to `cdn.telepatia.ai` is allowed (port 443)
* A policy management platform is available (ManageEngine, Intune, GPO, or equivalent)

## Policy Snippet

The extension is configured via the `ExtensionSettings` policy, natively supported by Chromium. Paste this JSON in your policy management platform:

```json theme={null}
{
  "fobdkddljbpmhnlclknlgcgbeeeojcnb": {
    "installation_mode": "force_installed",
    "update_url": "https://cdn.telepatia.ai/scribe-extension/update-manifest.xml"
  }
}
```

### Fields

| Field                              | Description                                                                                          |
| ---------------------------------- | ---------------------------------------------------------------------------------------------------- |
| `fobdkddljbpmhnlclknlgcgbeeeojcnb` | MV3 extension ID — stable, derived from the signing key                                              |
| `installation_mode`                | `"force_installed"` installs silently and prevents the user from disabling or removing the extension |
| `update_url`                       | Omaha XML manifest hosted by Telepatia. The browser checks this URL periodically for new versions    |

### Blocking other extensions (optional)

To allow only Scribe Companion and block all other extensions:

```json theme={null}
{
  "*": {
    "installation_mode": "blocked"
  },
  "fobdkddljbpmhnlclknlgcgbeeeojcnb": {
    "installation_mode": "force_installed",
    "update_url": "https://cdn.telepatia.ai/scribe-extension/update-manifest.xml"
  }
}
```

## Obtaining the CRX

For platforms that require a local CRX upload (e.g. ManageEngine via Upload Directly):

<Steps>
  <Step title="Check the manifest">
    Open `https://cdn.telepatia.ai/scribe-extension/update-manifest.json` from a workstation with internet access.
  </Step>

  <Step title="Download the MV3 CRX">
    Use the URL from the `v3.crx.downloadUrl` field.
  </Step>

  <Step title="Verify integrity">
    ```powershell theme={null}
    Get-FileHash -Algorithm SHA256 .\extension-v3-<version>.crx
    ```

    Compare with the `v3.crx.sha256` value from the manifest.
  </Step>
</Steps>

<Note>
  This is the starting version only. After installation, the browser auto-updates via the Omaha XML endpoint — no need to re-download for each release.
</Note>

## Deployment via ManageEngine Endpoint Central

<Steps>
  <Step title="Navigate to Browsers → Manage → Extension Repository" />

  <Step title="Add Extensions → Add Extensions for Google Chrome → Upload Directly" />

  <Step title="Upload the CRX file">
    ManageEngine registers it and displays the Plugin Identifier — confirm it matches `fobdkddljbpmhnlclknlgcgbeeeojcnb`.
  </Step>

  <Step title="Apply policy to target hosts/groups">
    Select by hostname, machine group, or department.
  </Step>

  <Step title="Wait for propagation">
    Target workstations receive the policy at the next agent sync.
  </Step>

  <Step title="Validate">
    Follow the [post-installation validation](#post-installation-validation) below.
  </Step>
</Steps>

## Deployment via GPO

<Steps>
  <Step title="Open Group Policy Management Console">
    Edit (or create) the GPO targeting the clinical workstations OU.
  </Step>

  <Step title="Navigate to the policy">
    **Computer Configuration → Administrative Templates → Google Chrome → Extensions → ExtensionSettings**
    (For Edge: same path under "Microsoft Edge".)
  </Step>

  <Step title="Enable and paste the JSON snippet above" />

  <Step title="Link the GPO to the target OU" />

  <Step title="Wait for GPO refresh (~90 min) or force with gpupdate /force" />

  <Step title="Validate">
    Follow the [post-installation validation](#post-installation-validation) below.
  </Step>
</Steps>

## Network Requirements

| Destination        | Port        | Purpose                              |
| ------------------ | ----------- | ------------------------------------ |
| `cdn.telepatia.ai` | 443 / HTTPS | Manifests, CRX download, auto-update |

<Warning>
  Blocking `cdn.telepatia.ai` silently prevents installation and all future updates. The workstation stays frozen on the installed version, missing bug fixes and security patches.
</Warning>

### SSL inspection

If the hospital performs TLS interception, configure an exception for `cdn.telepatia.ai`. Chromium validates the CRX cryptographic signature — some SSL inspection implementations modify headers that affect binary delivery.

## Auto-Update

After installation, the browser auto-updates the extension every \~5 hours (with jitter between \~2.5h and \~7.5h). No IT intervention needed.

To force a manual update check on a specific workstation:

1. Open `chrome://extensions`
2. Enable Developer mode
3. Click "Update"
4. Disable Developer mode after

## Post-Installation Validation

Validate on at least one pilot workstation:

<Tabs>
  <Tab title="Layer 1: Installed">
    * Open `chrome://extensions`
    * Confirm **Telepatia Scribe Companion** appears
    * Confirm it says *Installed by your administrator*
    * Confirm the user cannot disable or remove it
  </Tab>

  <Tab title="Layer 2: Correct ID">
    * In `chrome://extensions`, expand the extension details
    * Confirm the **ID** is `fobdkddljbpmhnlclknlgcgbeeeojcnb`
    * A mismatch means the wrong CRX or policy was applied
  </Tab>

  <Tab title="Layer 3: Auto-update works">
    * Enable Developer mode, click "Update"
    * Or validate connectivity:

    ```powershell theme={null}
    Invoke-WebRequest -Uri https://cdn.telepatia.ai/scribe-extension/update-manifest.xml -UseBasicParsing
    ```

    * HTTP 200 = path is open. Any other response = review network requirements
  </Tab>
</Tabs>

## Ongoing Operations

| Telepatia                                    | Hospital                                          |
| -------------------------------------------- | ------------------------------------------------- |
| Build, sign, publish new CRX versions        | Maintain the policy configuration                 |
| Maintain update-manifest endpoints           | Maintain host/group targeting                     |
| Notify on behavior changes or security fixes | Maintain HTTPS connectivity to `cdn.telepatia.ai` |
| Act on distribution incidents                | Report anomalous workstation behavior             |
| Rollback via manifest when needed            | Monitor propagation after policy changes          |

## Support

During installation, report unexpected behavior through the agreed channels with Telepatia. For operational urgency after deployment (workstations stop updating, anomalous behavior), use the established support channels.