LinkedIn publishing guide

LinkedIn Organization URN and Access Token.

LinkedIn publishing in Oryginal uses an author reference plus an OAuth token. For company workflows, that author reference is usually the organization URN in the format urn:li:organization:....

What each field does

The two LinkedIn values inside Oryginal

LinkedIn_Org_ID

Use the LinkedIn author URN that identifies the publishing account.

  • Company-page format: urn:li:organization:12345678
  • Profile publishing where applicable: urn:li:person:...
  • Do not use a company URL or public profile URL in this field.

LinkedIn_Access_Token

Use the LinkedIn OAuth access token that is allowed to publish on behalf of the selected URN.

  • Paste the raw token only.
  • The token must align with the app/member flow that can post for that author.
  • A valid token without author permission still fails at publish time.
Setup logic

How to keep the author and token aligned

  1. Decide whether the publishing flow is for a company page or a personal author.
  2. Copy the exact URN for that author reference.
  3. Retrieve the access token from the LinkedIn app/member flow that has permission to publish for that author.
  4. Store both values together in Oryginal without mixing organization and person credentials.

If you still need to create the app credentials, follow the LinkedIn API key setup guide. If you already have the Client ID and Client Secret, use the LinkedIn Token Helper to generate the OAuth link, exchange the authorization code, and prepare the final Oryginal values.

If your team publishes for a company page, keep the organization URN and the token inside the same company-page workflow instead of mixing personal and organizational references.

Common problems

What breaks LinkedIn publishing most often

  • Using a public URL instead of the author URN.
  • Copying an organization URN but using a token authorized only for a personal flow.
  • Copying a token that is technically valid but missing the needed publishing permission.
  • Switching from organization to person publishing without cleaning up the dashboard values.