Skip to main content

Setting Up LinkedIn Posting Permissions for Delegates

Learn how to properly set up LinkedIn permissions so your team members can publish posts on your behalf

Written by Junaid Khalid
Updated over 2 weeks ago

Before you invite editors or admins to your LiGo account, you must properly set up LinkedIn posting permissions. Failure to do this will result in your delegates receiving errors when they try to publish posts on your behalf.

Critical: Only you (the account owner) can connect your LinkedIn profile to your LiGo account. Delegates cannot use the Profile Switcher or any other method to link LinkedIn accounts to your LiGo account - this must be done by logging into your own LiGo account directly.

How to connect your LinkedIn account? Go to your account settings and ensure your LinkedIn account is connected. Only after completing this step should you invite delegates (Editors or Admins) to your account.


Important Cautions About LinkedIn Permissions

Permission Expiration

LinkedIn OAuth tokens have an expiration period (typically around 30-60 days). This means:

  • You may need to repeat the authentication process periodically

  • If a delegate suddenly can't publish posts, this is likely the reason

  • We recommend re-authenticating with LinkedIn every 30 days to prevent interruptions

Verifying Active Permissions

To check if your LinkedIn permissions are currently active: Go to your account settings and ensure your LinkedIn account is connected


What Delegates Will Experience

  • If permissions are properly set up, delegates can publish to your LinkedIn without issue

  • If permissions have expired, delegates will receive an error message when attempting to publish

  • Only you (the account owner) can renew the LinkedIn permissions – delegates cannot do this for you

  • Delegates cannot connect or reconnect LinkedIn profiles - they can only work with profiles that have already been connected by the account owner


Troubleshooting Common Permission Issues

Problem

Solution

Delegate gets Authentication Failed error

Account owner needs to re-authenticate with LinkedIn

Posts appear in LiGo but not on LinkedIn

Check LinkedIn permissions and re-authenticate

Permission Denied messages

Ensure the delegate has the correct role (Admin/Editor)

For persistent issues, contact support by clicking on the message icon on the bottom right of your screen with details about the specific error messages you're encountering & images if possible.


Common Questions

Q: Why do I need to connect my own LinkedIn account before inviting editors or admins?

Only the account owner can connect a LinkedIn profile to LiGo. Delegates cannot use the Profile Switcher or connect LinkedIn accounts on your behalf. If you invite delegates before connecting your profile, they will receive publishing errors.

Q: How do I connect my LinkedIn account to LiGo?

Go to your Account Settings and connect your LinkedIn account from there. Once your profile is fully connected, you can safely invite Editors or Admins to publish posts on your behalf.

Q: Why do LinkedIn posting permissions expire?

LinkedIn OAuth tokens typically expire every 30–60 days. When this happens, delegates will no longer be able to publish posts for you. Re-authenticate your LinkedIn account regularly about every 30 days to avoid interruptions.

Q: What happens if my delegate tries to publish but permissions have expired?

Delegates will receive an Authentication Failed or similar error message. Only you, the account owner, can renew permissions by reconnecting LinkedIn in your settings. Delegates cannot reconnect or replace your LinkedIn profile.

Q: How do I troubleshoot LinkedIn publishing issues in LiGo?

Try the following steps:

  • Authentication Failed: The account owner must re-authenticate with LinkedIn.

  • Posts appear in LiGo but not on LinkedIn: Reconnect your LinkedIn permissions.

  • Permission Denied: Confirm the delegate has the correct role (Editor or Admin).
    If issues persist, contact support with screenshots and the exact error message.


Related Resources


​

Did this answer your question?