Browser Extension · Step 3 of 7

Manual Installation

Install on a single device by hand — ideal for a pilot or a technician build. On macOS, install the configuration profiles before the package so permissions are granted before the agent runs. On Windows, a single MSI does everything.

🔗

Quilr Console Tenant artifacts (.pkg / .mobileconfig / MSI download links) live in Settings → Browser Extension → Deployment. The link below tracks the Environment selector in the top bar.

Open Console

Extension identity

The Quilr browser extension is identified by a fixed ID. After the MSI / pkg installs it, jump straight to its row in the extensions page using the direct deep-links below.

Extension name	Quilr
Extension ID	`piajhjohgigijkddhdpgbjdcfhmammbk`
Edge deep-link	`edge://extensions/?id=piajhjohgigijkddhdpgbjdcfhmammbk`
Chrome deep-link	`chrome://extensions/?id=piajhjohgigijkddhdpgbjdcfhmammbk`
Brave deep-link	`brave://extensions/?id=piajhjohgigijkddhdpgbjdcfhmammbk`

🔗

Why you can’t click these Browsers refuse to follow edge:// / chrome:// links from a regular web page (a hardening rule against drive-by extension prompts). Copy the URL with the Copy button above, then paste it into the browser’s address bar.

Prerequisites for this device

Tenant ID from Quilr support; admin rights on the Mac
Access to the Quilr console (https://app.quilr.ai/en/settings/browser-extension/deployment) for the tenant profile
Network reachability to quilr-extensions.quilr.ai

Download the three artifacts

macOS needs two required things — the tenant pkg + the tenant .mobileconfig for the extension — plus an optional third (the File-Access .mobileconfig) that can only be applied via MDM. On an unmanaged Mac, grant Full Disk Access by hand instead (see 1.3 below).

#	Artifact	Source	Tenant-specific?
1.1	Tenant pkg — `quilr-installer-mac.pkg`	`https://quilr-extensions.quilr.ai/<TENANT-ID>/browser-util/quilr-installer-mac.pkg`	yes
1.2	Extension `.mobileconfig`	Quilr Console → `/en/settings/browser-extension/deployment`	yes
1.3	File-Access `.mobileconfig` — optional	`https://quilr-extensions.quilr.ai/browser-agent/prod/mac/quilr_browser_util_Files_Access.mobileconfig`	no — shared & optional (MDM only)

1.1 — Tenant-specific package

bash

TENANT_ID="<TENANT-ID>"
curl -fsSL -o ~/Downloads/quilr-installer-mac.pkg \
  "https://quilr-extensions.quilr.ai/${TENANT_ID}/browser-util/quilr-installer-mac.pkg"

1.2 — Extension config profile (from Quilr Console)

Jump to Settings → Browser Extension → Deployment in your tenant Console. Under MDM, select macOS and “Manual / no MDM”, then download the .mobileconfig to ~/Downloads/. This profile carries the tenant-specific Chrome / Edge / Brave force-install policy.

1.3 — File-Access config profile (MDM only — optional on unmanaged Macs)

macOS only honours Full Disk Access (FDA) configuration profiles pushed by an MDM. sudo profiles install on the command line cannot grant FDA — the kernel ignores it. If your fleet is MDM-managed, download the profile and push it via Jamf / Kandji / Intune-mac. On an unmanaged Mac, skip the profile and use the manual toggle below.

bash — only useful when re-uploading to an MDM

curl -fsSL -o ~/Downloads/quilr_browser_util_Files_Access.mobileconfig \
  "https://quilr-extensions.quilr.ai/browser-agent/prod/mac/quilr_browser_util_Files_Access.mobileconfig"

🔑

Manual fallback — unmanaged Mac

Open System Settings → Privacy & Security → Full Disk Access.
Find quilr-native-messaging-agent-mac in the list (it appears once the pkg in step 1.1 is installed).
Toggle it On; authenticate with Touch ID or your admin password when prompted.

Without FDA, the native agent runs but can’t read browser cookie / history files — user identity attribution falls back to a less reliable signal.

Install the extension profile first

bash · sudo

sudo profiles install -path ~/Downloads/<tenant-specific>.mobileconfig

# File-Access profile (1.3) is MDM-only — `profiles install` cannot grant FDA.
# On an unmanaged Mac, grant FDA via System Settings (see 1.3 manual fallback).

Approve the extension profile when prompted in System Settings → Privacy & Security → Profiles. On an MDM-managed Mac the File-Access profile is delivered separately by your MDM and lands silently.

Install the package second

bash · sudo

sudo installer -pkg ~/Downloads/quilr-installer-mac.pkg -target /

The native agent installs and registers the WebExtension into your browsers automatically. Validate in Step 4.

↩️

Uninstall Run the supplied uninstaller script and remove the profiles by their PayloadIdentifier.

Download the MSI

PowerShell (admin)

Invoke-WebRequest 'https://quilr-extensions.quilr.ai/Quilr.msi' -OutFile $env:TEMP\Quilr.msi

Install with your tenant ID

PowerShell (admin)

msiexec /i "$env:TEMP\Quilr.msi" TENANT=<TENANT-ID> /qn /norestart

⛔

Note the parameter name For the extension MSI the property is TENANT (not TENANTID — that one is for the endpoint agent). Without it, the extension installs but stays idle.

Confirm

The MSI installs the native messaging agent and force-installs the WebExtension via browser policy. Open edge://extensions / chrome://extensions — Quilr should appear, enabled and “Installed by your organization.” Full validation is in Step 4.

✅

Exit criteria for Step 3 (macOS) both profiles installed then the pkg · (Windows) MSI installed with TENANT · the extension shows in the browser. Verify it’s actually working in Step 4.

←BackPrerequisites Validation Step 3 of 7 NextValidate Manual Install→