Skip to article

Integrations

LinkedIn

A LinkedIn profile or Company Page with posting permission

Ownership and availability

You own the LinkedIn member profile or Page. Obelo manages OAuth and publishes only after your approval.

Start in Settings → Integrations and check the provider’s current status. This guide describes the configured setup path, not a guarantee of production enablement. Provider approval, plan access and resource permissions still apply.

Before you connect

  • Administrator or content-admin access for an organization Page
  • The LinkedIn account must be eligible for the posting permissions granted to Obelo
  • An Obelo workspace owner or admin completes OAuth

Connect an existing account

  1. Open the provider in Settings → Integrations for the intended website.
  2. Sign in to the LinkedIn account that manages the target identity
  3. Review and approve the posting permissions
  4. Return to Obelo and confirm the selected member or organization identity

If you need a new resource

  1. Create a LinkedIn Company Page if the brand does not have one
  2. Complete the Page identity and assign the connector as an admin
  3. Publish the Page and return to authorize Obelo

Permissions to check

  • Member publishing uses w_member_social; organization publishing requires the approved organization permission and Page role
  • Obelo keeps approval and publishing as separate actions

Verify and troubleshoot

After the Page and admin role are ready, return and reconnect.

No publishable LinkedIn identity was returned. Confirm the signed-in account has the required Page role and that Obelo has provider approval.

Confirm the selected account or resource and inspect the verification or sync result. A saved connection is not proof that an import or publication has completed. Test the intended workflow with an appropriately reviewed item.

Disconnect or change access

Use the provider’s management controls in Obelo to disconnect when supported. Revoke the grant or rotate a dedicated credential at the provider if access must end immediately. Review already-imported data separately; disconnection does not remove content already published elsewhere.

Something unclear or out of date?

Suggest a correction