Part 2 · Set up
Connecting LinkedIn
Publishing to your own profile through the official API. Nothing automates your session.
01What it is
An official OAuth connection that posts to your own profile. It requests one scope and holds no other permission.
02Why it exists
LinkedIn is where most of this audience is, and posting there through the official API is both allowed and reliable.
What the product will never do is act inside your logged-in session. Tools that click and type on your behalf pass the ban risk to you, and that is your account rather than theirs. The browser companion observes and prepares; it does not act.
03How to use it
- 01Connect from Settings. One scope is requested and no more.
- 02Approve posts in the normal queue. Publishing happens after approval.
- 03Install the browser companion separately if you want your outreach tracked.
- 04Reconnect when a token is revoked. The panel says when that has happened.
04What good looks like
- You give it
- OAuth connected, posts approved in the queue.
- You get
- Posts appear on your profile at the scheduled time, published through the API.
- Why
- The publishing scope allows exactly this and nothing else.
Derived from the rules in the code
05What weak looks like, and what it costs
- You give it
- Expecting the browser companion to send connection requests for you.
- You get
- Nothing is sent. The companion records what you did and drafts what comes next.
- Why
- The extension holds no capability to click, type or submit, and the bundle test fails the build if one is added.
Derived from the rules in the code