What you are connecting

Pairing links this Chrome installation to your account and workspace. Facebook identity linking then identifies the person or Pages that may post through it. A successful pairing message is not enough if Facebook has not been linked.

Before you start

Use Chrome on your computer, signed in to the intended LeadKnight account and workspace. Facebook-group connection is not performed from a phone browser. Each personal Facebook profile needs its own browser/device where that profile is signed in. Do not pair your installation to somebody else's profile.

Install and connect automatically

Open Connections, the Facebook-group connection and its connection controls. Choose Install & connect or Install the extension where offered. The official Chrome Web Store listing opens in a new tab.
Install the extension from that listing, reviewing Chrome's permission request. Return to the app tab. The app waits for the installation and attempts to connect automatically.
If using the extension popup instead, choose Connect to LeadKnight. It opens the app's connection page at /connect-extension; sign in if needed.
If the connection page shows Connect, choose it. While it connects, the page displays Connecting your extension….
Open Facebook in this same Chrome profile and sign in to the intended account. Sign in to Facebook in this Chrome — we'll finish automatically. means Facebook identity discovery is still waiting.
When offered, review Choose your Facebook identities, then Connect selected. Check the displayed name and Posting as in the popup before preparing publishing work.
The connection page shows Connected as {name}; Continue to LeadKnight returns to the app. In Connections, inspect the selected profile's connection rather than only relying on the install having finished.

Use a code if automatic connection fails

In the Facebook-group connection controls, choose Enter a code instead and copy the current code with Copy.
Click the extension icon in the Chrome profile you want to connect, then Connect with a code. The extension's popup and options currently use English labels even when the app is Hebrew.
Paste into Connection code, then choose Connect. Wait for Connected or read Couldn't connect.
Return to Facebook and the app to finish identity linking and selection. If pairing was accepted but the extension has not checked in, keep Chrome open and use the app's retry action.

If this browser is already connected to a different profile or workspace, use the intended Chrome profile and manage the existing connection rather than overwriting another person's connection accidentally.

Check online status

Where	What to look for
Extension popup	Online, Offline or Not connected, plus Last post and Posting as when available.
Connections	The selected profile's extension strip and Manage connection.
Popup Settings	Technical details contains Last heartbeat, Last job and Last error when support needs diagnostics.

Online reflects recent check-ins, not proof that a particular post succeeded. Extension connected — Facebook identity not linked yet requires opening Facebook in the paired browser. If Facebook was already open before installation, navigate it again when appropriate so the extension can read the identity; save unfinished Facebook work first.

Keep the publishing browser available

Keep Chrome open and the Facebook session signed in while browser work is due. My browser only means posts wait if the extension is offline. The app describes Orbit 1 as working with the Facebook tab in the background and Orbit 2 as needing Facebook in front; there is no universal foreground requirement for every method. Do not close the browser assuming a paired status alone will perform the work. For WhatsApp sending, keep WhatsApp Web open too.

Updates

The store extension receives Chrome Web Store updates. Current versions can apply an available update without restarting Chrome, after pairing and running posting/sending work have finished. Closing the extension popup/options page when it is no longer needed avoids holding up an update. Older versions before 1.5.0 need Chrome fully closed and reopened to install updates; do this when no publishing is running.

If something goes wrong

Offline or Extension not running: open the paired Chrome profile, confirm the extension is enabled and Facebook is signed in. Queued posts with an offline explanation wait for reconnection; do not republish them.
Not connected or Not paired: complete the app connection or code flow in the correct workspace.
Identity not linked: open Facebook in that Chrome and inspect the popup's specific warning.
Waiting to switch Facebook: sign in as the linked profile. Another account in that browser cannot silently publish as the old one.
Profile limit or seat message: resolve the displayed profile allowance or Set up your seat before retrying.
Needs verification after a post: inspect the group before any retry; uncertainty is not permission to publish a duplicate.

Disconnecting the extension signs out all its paired installations and requires a new pairing code. The confirmation says your Facebook account, groups and posts remain untouched. Disconnecting a Facebook profile is a different action that stops publishing from that identity.

Install and connect the Chrome extension