Install it from our download.
The Chrome Web Store is the usual way in. When it is blocked on your network, or your IT team rolls extensions out by policy, install the same build from here. It pairs with your Tern account the same way.
Load unpacked, in about two minutes
Chrome 116 or newer. The zip is the build we submit to the store, packaged for a manual install.
- 1
Download the extension
Download latest.zip. It is the same build we submit to the Chrome Web Store, packaged for a manual install.
- 2
Unzip it to a folder you keep
Unzip into a folder that stays put, such as Documents/Tern Bridge. Chrome loads the extension from this folder every time it starts, so do not unzip into Downloads and do not delete the folder later.
- 3
Open chrome://extensions
Type chrome://extensions in the address bar and press Enter, or open the three dot menu, then Extensions, then Manage extensions.
- 4
Switch on Developer mode
The switch is in the top right corner of the extensions page.
- 5
Press Load unpacked
A folder picker opens.
- 6
Pick the folder you unzipped
Choose the folder that holds manifest.json directly (not the zip, not a folder above it). Tern Bridge appears in the list, switched on.
- 7
Pin it
Press the puzzle piece icon beside the address bar and pin Tern Bridge, so the bird is always one click away.
- 8
Open app.ternup.io and the panel pairs
Sign in to Tern in a tab. The extension pairs with your account on its own within a minute; the side panel then reads Paired and every site your organisation allows is on.
What a manual install means
Three things differ from a store install. None of them touch what the extension does on the page.
- Chrome shows a Disable developer mode extensions notice when it starts. It is expected for any extension loaded outside the store; press the X and it stays away until the next restart.
- Updates are manual. When a newer build is out, the side panel says Version x.y.z is available with a download link and the pill on the page shows a small dot. Download the zip, unzip it over the same folder and press the reload arrow on the Tern Bridge card in chrome://extensions.
- Load unpacked gives the extension an id of its own per folder. Nothing in Tern depends on it; pairing is by your account, not the id.
The version, size and sha256 of the current build are in latest.json.
A managed install by policy
Chrome enterprise policy installs and updates Tern Bridge on every managed browser without anyone pressing Load unpacked. It installs our packed CRX from its update manifest and keeps it current on Chrome's own schedule, so the developer mode notice and the manual update do not apply.
Extension id
ifkkaokngpnmeffgdhokhkknfpjakfakAn extension id is derived from the key that signed the package, so it is stable only for our packed CRX, which every release signs with the same key. A Load unpacked install gets an id of its own per folder and the Web Store listing has a third. Use this one in policy.
Policy values
ExtensionInstallForcelist
ifkkaokngpnmeffgdhokhkknfpjakfak;https://assets.ternup.io/public/bridge/update.xmlExtensionSettings
{
"ifkkaokngpnmeffgdhokhkknfpjakfak": {
"installation_mode": "force_installed",
"update_url": "https://assets.ternup.io/public/bridge/update.xml",
"toolbar_pin": "force_pinned"
}
}Set either through Google Admin (Chrome browser, Apps and extensions), Windows Group Policy or a macOS configuration profile. The update manifest at update.xml names the current CRX and version; Chrome checks it every few hours.
Ready to start?
Installed?
Sign in and it pairs.
Open app.ternup.io in a tab. The extension pairs with your account within a minute and the sites your organisation allows switch on.