Each PostedIn workspace uses its own LinkedIn developer app. The connection gives PostedIn permission to publish for the profile you authorise. You do not share your LinkedIn password with us.
1. Create your developer app
Open LinkedIn Developers and create an app. Give it a name you recognise, add its logo, and complete LinkedIn’s required fields. If the form requires a LinkedIn Page, it means an organisation Page rather than the personal profile you will publish to. Follow the Page verification instructions shown in your developer portal.
The app’s associated Page and the personal account authorising posting serve different purposes. During the connection step, sign in as the person whose profile should receive the posts.
2. Enable the two products
Under Products, request Share on LinkedIn and Sign in with LinkedIn using OpenID Connect. Posting uses the w_member_social permission; identity uses openid, profile, and email. Wait until the required products are available to your app before connecting.
If LinkedIn says you do not have access to the application, check the app’s product access and available OAuth permissions. Do not add unrelated advertising or organisation permissions just to try to clear the error.
3. Copy the redirect URL exactly
Open Integration in your PostedIn workspace. Copy the authorised redirect URL shown there into the OAuth redirect URL list in your LinkedIn app’s Auth tab. The scheme, hostname, path, and trailing slash must match the URL PostedIn uses.
Copy the Client ID and Client Secret from the LinkedIn app into your workspace. Save the settings before selecting Connect LinkedIn. Treat the Client Secret like a password: do not include it in screenshots, posts, or messages.
4. Authorise the right profile
Select Connect LinkedIn. LinkedIn opens its own sign-in and permission screen. Confirm the account, review the requested permissions, and return to PostedIn. The workspace should show the connected member’s name.
If the connection expires or cannot be verified, start again from the workspace. Avoid reusing an old authorisation URL or switching between browser sessions in the middle of the flow. If your LinkedIn access token later expires, reconnect from Integration.
5. Review before switching on automatic publishing
Check the prepared copy and images first. New workspaces use manual approval. When your batch is ready, choose automatic publishing, your timezone, and the daily hour. The next queued post is eligible after that hour, with at most one completed publication per local day.
On Free, PostedIn adds its signature at publishing time. Paid workspaces with an active month publish without it. If a request is interrupted after LinkedIn might have accepted it, check your real profile before retrying; the workspace can ask you to reconcile the result to avoid a duplicate.