Bluesky Publisher

Connect the intended account through AT Protocol OAuth and review text and media before sending a post. Review the destination and final content before confirming each publication.

Check the required Sense CMS Social Publishing capability, package compatibility and the account permissions shown during connection. Provider approval, account eligibility and configured access are independent of a signed download. Test the connection and review any provider error before retrying; a failed request is not proof that nothing was published.

This paid plugin requires its own product licence. The Sense CMS Core key and keys for other extensions do not authorize it.

Licence identity: Sense CMS Bluesky Publisher Plugin / Bluesky Publisher Plugin. The 32-character key, installation domain, start date and expiry date are validated independently. Compatible package updates retain the same product licence while it remains valid.

The exact signed development package is available from the Extensions marketplace. This is not a Stable release and requires the installed Sense CMS Social Publishing addon.

Bluesky currently does not require a paid API plan for this publishing flow. The Sense CMS annual fee funds extension development, compatibility maintenance and monitoring.

Connect one or more Bluesky-hosted accounts through AT Protocol OAuth. Editors choose destinations for every reviewed post and may customize the message per account.

The official client requests only the permission to create app.bsky.feed.post records. Sense CMS queues deliveries, prevents duplicates and records bounded retry history.

Access tokens, rotating refresh tokens and DPoP proof keys are encrypted inside the CMS installation. Account passwords never enter Sense CMS. The official confidential client key remains on the Sense CMS service.

Connections can be managed independently. Publishing always follows explicit editorial selection.

Compare themes, plugins, addons and applications with clear pricing and release availability.