Social Studio
Social Studio is for people who post regularly under their own name and want the drudgery removed without handing over the judgement. Write the words, plan when they go out, approve them yourself.
Find it under Social → Studio.
Connect an account first
Who and where → Connected accounts. Nothing can publish until at least one account exists here.
A post targets an account, not a platform. One person can run several pages, each with its own name and its own credentials, so “page principale” and “page ateliers” are separate destinations rather than one Facebook setting.
Three ways to connect, and the app only offers the ones a given platform actually accepts:
- Sign in — the platform hands back a token.
- API keys — paste credentials from the platform’s developer console.
- Webhook URL — the post is sent to a URL. No developer account needed.
The webhook option is the useful escape hatch: anything that accepts a webhook POST works with no new code, including Slack, Teams, Zapier, Make, n8n, or an endpoint you wrote yourself.
Platforms that cannot publish yet are listed with the reason rather than hidden. A platform quietly missing from a dropdown is how a month of posts ends up scheduled somewhere they would never appear.
Whose name is on it
Who and where → Who is posting. Two fields, deliberately separate:
- Your name — recorded against every approval. This is what the plan answers with when someone asks who published a thing.
- Card signature — what gets drawn on the card itself, which may be a page or practice name rather than a person.
Compose
Type the sentence, pick a size and a background, render. The preview reports line count, font size, and the measured contrast between your text and the background, so you know a card is legible before it is a post rather than after.
If no usable font is found, the app says so instead of drawing empty boxes where the accented characters should be.
Plan a batch
The part that saves real time. Paste a month of quotes — one per line, or separated by blank lines for longer posts — pick the weekdays and times, and the dates are worked out for you.
The split and the dates are shown before anything is created, because one post silently becoming five is only noticed after twenty drafts exist.
Times are yours, not UTC. Nine in the morning means nine in the morning where you are.
Duplicates are detected ignoring case, accents and punctuation, so a line retyped slightly differently is still caught. They are reported, not blocked — sometimes reposting is the point.
Approval
Nothing is publishable until a named person approves it. There is no approve-all, no auto-approve, and no publish button; the backend has no route for one.
- Approving requires typing a name, which is recorded against the post.
- Editing an approved post revokes the approval. Approval belongs to the words, not to a slot in a calendar.
- Posts written with AI assistance carry a visible badge until they are approved, so the decision is made knowing where the wording came from. They get no shortcut.
- A post addressed to an account you have since disconnected cannot be approved, and cannot publish. That is checked when you approve, again immediately before sending, and again in the scheduled sweep.
Export
Export writes the whole plan to a folder: one text file per post, a CSV index, and the card images copied alongside. The CSV opens in Excel with accented characters intact.
This exists so the scheduler is never the only way to reach your own content. If a connection lapses, or you would simply rather post by hand that week, everything is sitting in a folder.
Credentials never appear in an export. That folder is something you might email to a colleague, so it is tested to contain no key, token or webhook URL.
Something here wrong or missing? Tell us — documentation that describes software that no longer behaves that way is worse than none.