Cannot connect a second LinkedIn account (personal + company page/company page + showcase pages) in the same workspace

[fedemic]

Describe the bug
When connecting LinkedIn, the OAuth flow shows a screen letting one choose between personal profile and company pages the account manages. However, only one selection can be active per workspace at a time.
The Social Accounts page shows a single LinkedIn card, and to connect a different LinkedIn destination I first have to disconnect the existing one, rather than adding it as an additional account.

I'd expect to be able to keep multiple LinkedIn connections (e.g. my personal profile + a company page or company page + showcase pages) simultaneously in the same workspace, as other solutions do.

Steps to reproduce

1. Connect LinkedIn, choose your personal profile or a company page in the account selector
2. Go to Social Accounts → try to connect LinkedIn again, this time choosing a different destination (e.g. a company page instead of the personal profile)
3. New connection is not allowed as the only option is to disconnect the linked account.

Environment

• Self-hosted via compose.prod.yaml
• Latest image as of July 2026

[paulocastellano]

Hey Federico — thanks for writing this up.

This is intentional for now. On TryPost Cloud we bill per workspace, and social connections (including LinkedIn personal vs company page) are scoped to that workspace. Keeping a single LinkedIn destination per connection path in a workspace is part of that model.

On self-hosted, you’re not limited by that billing model — the usual approach is to create one workspace per brand/client (or per LinkedIn destination you need side by side) and connect the matching LinkedIn profile or company page there. That way each workspace stays focused, and you can still manage personal + company page (or multiple pages) across workspaces.

One idea we’re considering: allow multiple LinkedIn connections in the same workspace only for self-hosted, while keeping the current single-connection behavior on Cloud. We’re tracking multi-LinkedIn-in-one-workspace as a product ask, but it’s not a bug in the current design. Happy to hear more about your self-hosted setup if a multi-workspace layout doesn’t fit your workflow.

[HafizMMoaz]

Opened #286. Turns out the backend already supported this in self-hosted mode - SocialAccountObserver bypasses the one-account-per-network guard when trypost.self_hosted is true, and there was already a passing test proving a second LinkedIn organization could be connected that way. The actual blocker was the frontend: NetworkConnectGrid.vue collapsed a network to a single card the moment any account existed, with no way to trigger another OAuth flow.

Fix exposes self-hosted mode to the accounts/onboarding pages and renders one card per connected account plus a standing "Connect another" card for self-hosted deployments, while hosted mode keeps its existing one-per-network behavior. Backend tests passing (204), frontend build/typecheck/lint clean - flagged in the PR that I couldn't do a live browser smoke test with real LinkedIn OAuth in this environment, so worth a manual check before merging.

[fedemic]

I ran a manual end-to-end test and verified that multiple pages/profiles can be successfully added, and post publishing works correctly across the different channels. Thanks @HafizMMoaz! 🚀

@paulocastellano can we merge #286, or do you think anything else is needed?

[paulocastellano]

Hi @fedemic

Thank you, i will check it today!

[paulocastellano]

it's merged @fedemic @HafizMMoaz