Choose LinkedIn context
The customer chooses whether the intended workflow is for a LinkedIn member account or an organization Page.
Platform guidance
LinkedIn workflow guidance
LinkedIn workflows are intended for authenticated member or organization use cases where LinkedIn platform permissions allow.
Overview
What this page covers
This page gives customers and platform reviewers a public summary of how Braineek describes LinkedIn workflows. It is not an internal setup guide and does not expose private app configuration, callback URLs, secrets, tokens, or backend implementation details.
Requirements
Account and permission requirements
- Supported account type
- Authenticated LinkedIn member or organization account where permissions allow.
- Permission and approval caution
- LinkedIn documentation identifies member and organization posting permissions and organization role requirements.
- User control
- The customer controls which LinkedIn account authorizes access and whether a member or organization workflow is used.
Authorization flow
How LinkedIn authorization works
Authenticate with LinkedIn
The customer authenticates with LinkedIn through the platform authorization flow.
Review permissions
The customer reviews requested member or organization permissions before authorizing access.
Confirm Page role
For organization workflows, the customer should confirm they have the required role for the target LinkedIn Page.
Use granted access
Braineek can operate only within the granted permissions and the selected member or organization context.
Disconnect access
The customer can disconnect access through Braineek support paths and LinkedIn account controls.
Customer checks
Before authorizing Braineek
- Confirm whether the workflow is for a member profile or an organization Page.
- Review LinkedIn permissions requested during authorization.
- Use organization workflows only where the user has the required Page role.
Use cases
Supported workflow direction
- Member post preparation
- Organization post preparation
- Approval-ready campaign content
Implementation boundary
Public guidance, not internal configuration
Member and organization scope
LinkedIn workflows should distinguish between authenticated member use cases and organization Page use cases.
Permission and role boundary
Official LinkedIn documentation identifies member and organization posting permissions, with organization workflows depending on the user role for the target Page.
Publishing availability caution
Braineek can support post preparation and publishing workflows only where LinkedIn platform permissions and customer authorization allow.
Trust links
Disconnection, deletion, and policy pages
Customers should be able to disconnect connected accounts and request data deletion through Braineek support and the platform-specific controls available in their connected account.
LinkedIn questions
Customer-facing LinkedIn questions.
Why does account type matter for LinkedIn?
LinkedIn member and organization workflows have different permission and role expectations, so the customer should verify the intended account before authorizing.
Next step
Plan LinkedIn workflows with clear permissions
Discuss account eligibility, permissions, and review expectations before planning connected platform workflows.