Manifest V3 Installation

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.

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 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:

{
  "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:

{
  "*": {
    "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):

Check the manifest

Open https://cdn.telepatia.ai/scribe-extension/update-manifest.json from a workstation with internet access.

Download the MV3 CRX

Use the URL from the v3.crx.downloadUrl field.

Verify integrity

Get-FileHash -Algorithm SHA256 .\extension-v3-<version>.crx

Compare with the v3.crx.sha256 value from the manifest.

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.

Deployment via ManageEngine Endpoint Central

Navigate to Browsers → Manage → Extension Repository

Add Extensions → Add Extensions for Google Chrome → Upload Directly

Upload the CRX file

ManageEngine registers it and displays the Plugin Identifier — confirm it matches fobdkddljbpmhnlclknlgcgbeeeojcnb.

Apply policy to target hosts/groups

Select by hostname, machine group, or department.

Wait for propagation

Target workstations receive the policy at the next agent sync.

Validate

Follow the post-installation validation below.

Deployment via GPO

Open Group Policy Management Console

Edit (or create) the GPO targeting the clinical workstations OU.

Navigate to the policy

Computer Configuration → Administrative Templates → Google Chrome → Extensions → ExtensionSettings (For Edge: same path under “Microsoft Edge”.)

Enable and paste the JSON snippet above

Link the GPO to the target OU

Wait for GPO refresh (~90 min) or force with gpupdate /force

Validate

Follow the post-installation validation below.

Network Requirements

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

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.

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:

Open chrome://extensions
Enable Developer mode
Click “Update”
Disable Developer mode after

Post-Installation Validation

Validate on at least one pilot workstation:

Layer 1: Installed
Layer 2: Correct ID
Layer 3: Auto-update works

Open chrome://extensions
Confirm Telepatia Scribe Companion appears
Confirm it says Installed by your administrator
Confirm the user cannot disable or remove it

In chrome://extensions, expand the extension details
Confirm the ID is fobdkddljbpmhnlclknlgcgbeeeojcnb
A mismatch means the wrong CRX or policy was applied

Enable Developer mode, click “Update”
Or validate connectivity:

Invoke-WebRequest -Uri https://cdn.telepatia.ai/scribe-extension/update-manifest.xml -UseBasicParsing

HTTP 200 = path is open. Any other response = review network requirements

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.

Getting Started

Institution Installation

Features

Floating Panel

Extension ID

Prerequisites

Policy Snippet

Fields

Blocking other extensions (optional)

Obtaining the CRX

Deployment via ManageEngine Endpoint Central

Deployment via GPO

Network Requirements

SSL inspection

Auto-Update

Post-Installation Validation

Ongoing Operations

Support

​Extension ID

​Prerequisites

​Policy Snippet

​Fields

​Blocking other extensions (optional)

​Obtaining the CRX

​Deployment via ManageEngine Endpoint Central

​Deployment via GPO

​Network Requirements

​SSL inspection

​Auto-Update

​Post-Installation Validation

​Ongoing Operations

​Support

Extension ID

Prerequisites

Policy Snippet

Fields

Blocking other extensions (optional)

Obtaining the CRX

Deployment via ManageEngine Endpoint Central

Deployment via GPO

Network Requirements

SSL inspection

Auto-Update

Post-Installation Validation

Ongoing Operations

Support