Home AI Consulting First Contact About Us Login DE
Home AI Consulting First Contact About Us Login DE

LinkedIn Integration

LinkedIn Integration – Overview

On this page, we provide full transparency regarding how our platform connects to LinkedIn, the permissions used, how data is processed, and how users maintain control at all times.

This page remains permanently visible to the public and serves as a central source of information for both users and LinkedIn reviewers regarding the implementation.

1. Use Case

companycore ai allows registered users to create LinkedIn posts – either completely manually or with the help of an individual AI agent that generates tailored post copy and media suggestions based on information provided by the user.

Every post must be manually reviewed, confirmed, and scheduled with a date and time by the user.

Only after this active approval is the post automatically published to LinkedIn at the intended time via a scheduled process (cron job).

No automatic publishing takes place without prior, express user confirmation.

  • No automatic AI publishing
  • No auto-posting without manual confirmation
  • Posts are created exclusively after user interaction
  • Tokens are stored securely & can be deleted at any time

2. Integration Screenshots

a) Connection Status – Not Connected

This is what the interface looks like before a user connects LinkedIn:

LinkedIn not connected

b) Connection Status – Connected

After successful OAuth authentication, the user sees this status:

LinkedIn connected

c) New Post – Before Scheduling

Users create posts via the editor interface. The post is only entered into the calendar after active confirmation.

Creating a new post

d) A Scheduled Post in the Calendar

After confirmation, the post appears in the calendar and is marked for automatic publishing:

Scheduled post in the calendar

(These screenshots - except for the Connected status - show the actual representation in the app.)

3. Note on the LinkedIn OAuth Screen

Important for Reviewers:

The original LinkedIn OAuth dialog (“Authorize Application”), through which users can connect their LinkedIn account, will be fully displayed here as soon as LinkedIn has approved our application for the use of the corresponding Marketing or Community Management APIs.

We will provide the official OAuth screenshot on this page immediately after approval, so that reviewers and users can fully inspect the exact dialog, including all permissions used.

Placeholder for the OAuth screenshot

4. LinkedIn Permissions (Scopes) Used

  • w_member_social – Posting on behalf of the user
  • w_organization_social – Posting on behalf of a company page
  • rw_organization_admin – Verifying administrator rights on pages

5. Technical Publishing Process

  1. The user creates the post via an AI-supported editor where text suggestions are generated individually for them. Alternatively, the user can enter the entire text themselves. The user reviews, edits, and confirms the post completely before it is saved.
  2. The user manually sets the date and time of publication or saves the post as a draft. Only an actively scheduled post will be published automatically later.
  3. The post appears in the calendar as "Scheduled".
  4. A secure cron job triggers the publication at the scheduled time exclusively for posts previously actively scheduled by the user.
  5. Only posts with valid user confirmation (manually scheduled) are published.

6. Processing & Storage of LinkedIn Data

We store exclusively:

  • Access Token
  • Refresh Token
  • LinkedIn User-ID (URN)
  • IDs of the company pages for which the user has administrator rights.

We do not store LinkedIn content such as:

  • Posts
  • Followers
  • Contacts
  • Comments
  • Profile information

We only access LinkedIn data that is technically required for the publication of posts.

Tokens are stored exclusively in encrypted form.
The technical implementation is carried out according to LinkedIn requirements (AES-256 at the application level + encrypted database).

All stored LinkedIn tokens can be deleted at any time by the user disconnecting the connection to their LinkedIn account. After disconnection, all tokens are completely removed from our system.

7. Revocation & Deletion of Connection

Users can disconnect the connection at any time via the "Disconnect LinkedIn Connection" button in the app.
All stored LinkedIn tokens and associated data will be completely deleted within 24 hours.


This page is continuously updated and expanded as LinkedIn grants additional approvals or activates new functions. Any change to permissions or processes will be transparently documented here.