Know what each account can do.
Reach lists every connected account with its identity and connection state, and checks separately whether it can publish and whether it can read analytics. When a platform needs you to reconnect, it says so.
LinkedInCan publish · analytics waits on a platform permissionConnected
XNot connected yetComposer
YouTubeNot connected yetComposer
InstagramMeta adapter on the wayOn the wayThree steps.
Connect
Authorise an account on the platform’s own sign-in.
Check
Reach asks the platform what this connection may do.
Reconnect when needed
Expiring or reduced access is flagged before posts fail.
What you get.
From the Reach dashboard, as it works today.
Connection state
Not configured, pending approval, connected, degraded, reconnect required, or proven.
Publish and analytics, separately
An account can be allowed to post but not to read stats; Reach shows both.
Live check
A probe asks the platform directly instead of trusting a stored flag.
Credentials stay on the server
Tokens never reach the browser, and the check result carries none.
Per organisation
Each workspace sees only its own accounts.
Reauthorise
Reconnect an account in place without losing its posts.
Accounts you can publish to.
ConnectedConnected and proven on staging. Publishing is checked separately from analytics, which waits on a LinkedIn permission.
In the composerIn the Composer provider list. Posts and threads.
In the composerIn the Composer provider list. Video uploads with title and description.
In the composerIn the Composer provider list. Long-form articles.
In the composerIn the Composer provider list. Developer articles.
In the composerIn the Composer provider list. Developer blog posts.
In the composerIn the Composer provider list. Announcements to a server channel.
In the composerIn the Composer provider list. Email editions.
The other screens.
Your channels, on one calendar.
AI drafts. A person approves. Reach publishes on time and keeps the record.