From a connected account to a published post, and back again

An admin opens Connections and signs in to each network through that network's own consent screen. The panel asks for the narrowest permissions the features you use actually need, and stores the resulting access encrypted. Nothing is published to an account until it is connected here, and disconnecting it clears that access immediately.

One draft, then pick which accounts it goes to. Where a network needs different wording it gets its own caption; where it needs a title, a privacy level, or a first comment, those are fields on that network's tab rather than a compromise everyone shares.

Media is checked here, against the real limits of every network you selected. A file that is too long for TikTok, too large for a Reel, or the wrong shape for a Short is named while you are still editing.

Choose a time and the post joins the queue, one entry per account. The calendar shows the month, the queue shows the next fortnight. Where a network will hold a scheduled post itself, and Facebook is the only one that will, the panel hands it over and says so on the post.

A worker runs continuously and wakes every minute. It takes each due account in turn, claims it so that no two runs can publish the same thing, and calls the network. Work that can usefully start early does: a YouTube upload begins before its minute so that a large file is in place when the time comes.

Each account's entry carries its own status, so a post that lands on four networks and stalls on the fifth is exactly that, not a failed post.

A refusal that might succeed later is retried after a minute, then five, then fifteen, and no more than three times in total before the entry is marked failed and left for a person. The platform's own error is translated into a sentence that says what to do about it, and kept alongside the attempt that produced it.

If the panel loses its connection in the middle of a publish, it does not simply try again: it asks the network whether the post exists first, and adopts it if it does. A duplicate post is worse than a late one. When neither the network nor the panel can say, the entry is parked for review rather than resolved by guessing, and a post the network is still processing two hours later is parked the same way.

After a post is live, the panel gathers its figures on a schedule and keeps them, so a month-old post still has its numbers. Comments and mentions arrive in the inbox, account followers and totals build up over time, and Insights turns them into a series you can filter, compare, and export.