From the first idea to the published post
How it works
social.9of.de
Every post in on fleek Social takes the same route: the on fleek team prepares it, the contact person at the client company reviews it in their own account and approves it, and only then does the platform publish it to the client channels at the scheduled time.
This page describes that route step by step — who does what and when, what the application handles on its own, and what happens when a platform rejects a post.
The route a post takes
From connecting an account to the outcome of the publishing run.
- 1
Connect the account
The owner of the social media account authorizes it for on fleek Social via OAuth — on the sign-in page of the platform itself, with the permissions shown there. An account password never reaches us. The connection can be removed inside the application and revoked at any time in the app settings of the platform. The state of every connection is visible: connected, expiring, disconnected or error.
- 2
Create the post and upload media
A post is written once and is given its targets: one or several of the client accounts. The caption applies to all selected channels and can be overridden per channel. Images and videos are checked against the rules of the respective target type while they are uploaded — format, aspect ratio, duration, file size — so that an unusable video shows up straight away instead of at the moment of publishing.
- 3
Submit for approval
Submitting moves the post into the status “awaiting approval”, and the application stores a snapshot of that version. The contacts on file for the client company receive an email with a link to the post in their own account.
- 4
The client reviews and decides
The client account shows the full post with its media and caption, the channel-specific versions of the text and the list of target channels. The contact person can comment, request changes or approve. If changes are requested, the post goes back to the on fleek team; the revised version is submitted again and recorded as a new version, so it stays traceable what was changed.
- 5
Schedule the post
An approved post is given its publishing time in the calendar — month and week view, time zone Europe/Berlin — and counts as scheduled from that point on. Times can be moved as long as publishing has not started yet.
- 6
Publish automatically
At the scheduled time the queue picks the post up: one separate job per target channel, through the official API of the platform. Every job records its own result, so that a retry continues where it was interrupted instead of posting a second time.
- 7
Record the result
After the run, the post shows for each channel whether it was published; for Instagram and YouTube it also carries the link to the published post. TikTok and Facebook Pages return no link through their APIs, so there it stays with the status per channel. Figures such as reach or interactions are not evaluated by the application at this point; that is being prepared. What is visible today is the follower count, taken over when an account is connected and shown on the account card, plus the overview of open approvals, scheduled posts and failed publications.
Nothing is published without approval
The step into publishing depends on the approval status: posts are published exclusively from the statuses “approved” and “scheduled”. Every change of status runs through a single checked transition function and leaves an audit entry with the time and the person who triggered it. There is no way to get a post onto a channel past that check.
Whether a client company has to approve every post is decided per company. For the channels of on fleek GmbH itself the approval loop is switched off; there the team approves its own posts — which is just as much a logged transition of the same status machine.
Who does what
Two sides work on the same post, with clearly separated tasks and separate accounts.
The on fleek team
The contact person at the client company
- Whether posts require approval, and after how many hours without a response a reminder goes out, is configured per company.
- The email recipients for submissions and reminders are stored per company as well; if that list is empty, the emails go to every account of that company.
- Clients can contribute drafts of their own, with caption and media. The on fleek team picks them up, finalizes them and submits them for approval in the regular way.
- The connected accounts and channels belong to the client company. If a connection is removed or revoked at the platform, access ends.
What happens when something goes wrong
External APIs fail, reject content or take longer than expected. The application treats that as the normal case, not as an exception.
- If a channel fails and the disruption is temporary, the queue repeats the attempt with growing intervals — three times at most.
- After that the target is marked “failed”, together with the message the platform returned. That message is stored and displayed, never swallowed.
- If only individual channels are affected, the post counts as partially published: the successful channels stay online, the failed ones can be triggered again one by one.
- A second attempt never posts anything twice. For every target it is recorded whether, and under which identifier, it has already been published; uploads that were started are resumed instead of begun again.
- If an attempt ends without success for good, a notification goes to the on fleek team — a post does not quietly disappear from the schedule.
- If an account connection has expired or been revoked, the application reports that to the team as well and offers to reconnect the account in the interface.
Notifications
Everything that has to reach someone goes out by email. The application never sends messages through the connected social media accounts.
- Submission: email to the contacts of the client company, with a link to the post in the client account.
- Reminder: if a post has been waiting for a response longer than the configured period — 48 hours by default, adjustable per company — a reminder goes to the same contacts. Exactly once per round of submission, so that one reminder does not turn into a series; submitting again starts a new round.
- Change request: notification to the on fleek team as soon as a client requests changes.
- Publishing error: notification to the on fleek team when a target fails for good.
- Account connection: notification to the on fleek team when access expires or breaks off and the account has to be connected again.
Questions about the process?
on fleek GmbH · Industriestr. 10 · 92360 Mühlhausen · Germany. We answer questions about the approval process, about connected accounts and about the deletion of data.