Posts and destinations
How shared content, destination adaptations and delivery fit together.
A collection announcement might need a short Bluesky message and a longer LinkedIn post. In Postdot, they can share a source while keeping their own content and publication dates.
One post, several publications
The post holds the shared source: its title, text and media. Each destination gets a publication with its own adaptation, schedule and execution history.
| Item | Collection announcement example |
|---|---|
| Post | The announcement's shared text and images |
| Bluesky publication | A short message scheduled for Friday morning |
| LinkedIn publication | A longer introduction scheduled for Friday afternoon |
Editing the source does not overwrite destination adaptations or past publications. Applying a source update to an existing destination requires an explicit review action. Saving the source sends nothing.
You can also add a destination to an existing post. The new destination starts as a draft from the saved source; existing publications stay unchanged.
Where channels and publishers fit
A channel describes the destination and its content requirements. A connected publisher supplies the connection for automated delivery. A manual channel has no publisher: you deliver the content yourself and record the result in Postdot.
These connections belong to the project, rather than the person who connected them. Project access and permission to edit determine what a member can do.
A saved draft is not a delivery result
A publication can be a draft, be scheduled for delivery, or have a published or failed result. Check its delivery state rather than assuming that saving content or reaching the scheduled time means the destination received it.
An ambiguous outcome means the provider result is uncertain. Check what happened before retrying, since another attempt could send the content twice.
Follow your first publication to try this workflow in Studio, or connect a provider to set up a destination.