[Publish] How to connect a LinkedIn Company or Showcase Page



LinkedIn Profiles and Pages can be connected to your Buffer Publish account. In order to connect a LinkedIn Page, Buffer will need to authenticate through your personal LinkedIn Profile. Therefore, your Profile will need to have administrative privileges on the Page you're looking to connect.  Click here for more information on LinkedIn Admin roles.

Whilst Buffer Publish authenticates your LinkedIn Pages through your personal Profile, we won't access your personal information or post on your Profile (unless you have explicitly connected your Profile connected as another social account).

How to connect your LinkedIn Company or Showcase Page

LinkedIn Pages are connected in the same way as connecting other social accounts, with the additional step of selecting the Page you'd like to connect. We've found the quickest way is to first log into your LinkedIn Profile that has the required permissions. Here are all the steps you'll need:


Log in to your personal LinkedIn Profile that has the required permissions at  https://www.linkedin.com/


Log in to your Buffer Publish account at  https://buffer.com/app


If you're on the Free Plan, click the Connect More button at the bottom left of your dashboard and then click Page under the LinkedIn option.

If you're on a paid plan (Pro, Business, Enterprise), click on the  Add a Social Account button at the top left of your dashboard and then choose LinkedIn Page.


Since you're already logged into your LinkedIn Profile, you won't need to enter your login credentials. All you'll need to do is click on the Page you'd like to connect. From there, you should be all set!

Unfortunately, it is no longer possible to connect LinkedIn Groups to Buffer Publish. On 27th September, 2017, LinkedIn officially retired the previous API, meaning third party apps such as Buffer, were no longer able to post to Groups on behalf of a user. You can read more about this here.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.