Provider connections
Connect a publishing account to a channel in your project.
Choose the provider you want to connect:
| Provider | What you need | Guide |
|---|---|---|
| Bluesky | Account handle and OAuth; local or public client configuration | Connect Bluesky |
| Mastodon | Account and instance origin; OAuth application registration is automatic | Connect Mastodon |
| Configured OAuth application and member or organization access | Connect LinkedIn | |
| X | Configured OAuth 2.0 application with publishing access | Connect X |
| Discord | Bot token and destination channel ID | Connect Discord |
| DEV.to | Account API key | Connect DEV.to |
Who configures what?
The installation administrator manages the OAuth applications for Bluesky, LinkedIn and X. Project members with the required editing access connect publishing accounts from their channels. A configured application is not a connected social account: you still authorize the account you want that channel to use.
Connect from Channels in Studio with a human session. A Postdot API key does not replace that session or serve as a social network token. Social account login is separate from signing into Postdot.
Check the result
After connecting, inspect the destination account shown on the channel. Prepare an unscheduled draft first. A successful connection confirms authorization; it does not prove that every format, media file or future delivery will be accepted.
If access is revoked or the channel asks you to reconnect, start a fresh connection from Studio. Do not reuse a callback URL from browser history. For failed or uncertain deliveries, inspect the publication result before retrying a send.
No social account is required to use a manual channel. Its publication workflow records work that you complete outside Postdot. See your first publication for that alternative.