Personal vs Brand

Personal vs Brand posts

What it is

ProPresence has a global context switcher in the top bar. Everything you do is in one of two contexts:

  • Personal — your own LinkedIn profile. Author = you.
  • Brand — a LinkedIn company page belonging to an organization you manage. Author = the org.

The same article can be written once and pushed to either context. The plumbing underneath is completely different.

How they differ

Personal Brand
Author You The organization
Tone of Voice used Your personal ToV The org’s ToV
Publishing method Direct via your LinkedIn token Via Make.com webhook → LinkedIn company page
Token expiry 60 days, manual reconnect None on ProPresence side; depends on your Make scenario
scheduled_at behaviour Required for scheduling; defaults to 8 AM local Must be omitted on first push. Setting it fires the webhook immediately.
Lexi autopilot Personal Lexi cadence Per-organization Lexi cadence; only fires if webhook is active
Badge on the post card Blue Personal Coloured org badge with logo

How to switch context

  • Click your avatar/org logo in the top bar to swap.
  • Lexi auto-selects the active webhook organization when you switch into Brand mode.
  • Most pages remember the context per-tab.

Why brand posts must be drafts first

Make.com scenarios fire on the post.scheduled event. The moment a brand post has scheduled_at set, the webhook is called and the post goes live on the company page.

There’s no “review then publish” round-trip in the LinkedIn API for company pages, so ProPresence treats scheduled_at as the explicit publish trigger for brand content. If you want a review step, build it into your Make.com scenario (e.g. route through a Slack approval before posting).

Common mistakes

  • “My brand post went live before I edited it.” You set a schedule. For brand posts, leave scheduled_at empty until the draft is final.
  • “Lexi isn’t posting for my brand.” The org doesn’t have an active Make.com webhook. Set one up under Organizations → Webhook.
  • “Wrong tone on the brand post.” The org’s Tone of Voice is empty or wrong. Edit it under Organizations → Tone of Voice — it’s a separate ToV from your personal one.

Related: Make.com webhook setup, Lexi for organizations, Troubleshooting