Chrome extension and posting

What the extension does

The extension connects your own Chrome browser to LeadKnight and performs publishing work you approve using your signed-in accounts. It is the browser connection for Facebook-group posting. It also supports campaign sending through your own WhatsApp Web session; that number needs its separate sending connection.

The backend manages the campaign and publishing jobs. The extension performs work and reports results; installing it is not a publishing approval and does not by itself select campaign destinations.

Setup and everyday use

• Install and pair: use the Chrome Web Store, connect the browser and check status.
• Posting presets: choose Automatic or Manual settings, posting times and the available device choices.
• Facebook groups: confirm the identity, sync groups and organize folders.
• Cloud phones: understand the separate connected device where that feature is offered.

Why Chrome asks for permissions

Chrome may use broad wording for permissions. These are the extension's specific uses:

Permission	Purpose
storage	Keep the installation's pairing credential and connection/session state in Chrome. This is necessary to recognize the paired installation.
alarms	Wake the extension's background worker for scheduled connection and job checks.
scripting	Run the bridge used to read the signed-in Facebook identity and operate the approved publishing flow on Facebook.
declarativeNetRequest	Apply the Facebook-specific request rule that supplies the expected Origin header for the user's posting requests.
debugger	Perform reliable interactions with the user's Facebook posting tab, especially for photo/video publishing, using Chrome's debugging protocol. It is not permission for a support person to browse your computer.
Facebook site access	Identify the signed-in Facebook account and carry out approved posting work in that session.
WhatsApp Web site access	Connect the sending number and carry out approved campaign sends through WhatsApp Web.

When the debugging connection is attached, Chrome shows a bar at the top of the window saying that "LeadKnight" started debugging this browser (the exact wording follows your Chrome language). The permission justification scopes debugging to the Facebook tab used for publishing, not arbitrary tabs or unrelated browsing traffic. Do not dismiss the message by assuming a connection problem; check whether approved publishing is running.

For WhatsApp campaign sending, the product scope is outgoing messages and group synchronization, not reading or storing incoming replies. The assistant's WhatsApp connection is separate.

Connection is not identity or delivery proof

The extension popup shows Status, Last post and, when available, Posting as. A browser can be paired while its Facebook identity still needs linking, or while Facebook is signed out. Check both the extension state and the identity in Connections.

A post marked Needs verification is not confirmed as delivered or failed. Check the group before retrying. If the extension is offline and the result says the queued post will go out after reconnection, restore the connection rather than publishing a duplicate.

Privacy and account responsibility

Pairing authenticates this browser to your workspace; it does not transfer ownership of your Facebook account to another teammate. Read the privacy policy before granting access. Account permissions and publishing approvals still apply, and you remain responsible for the platform's terms.