Use case
Get client sign-off before a post goes out.
Get client sign-off before a post goes out
By hand today
Captions pasted into email or a shared document, then re-pasted back with edits
In Synclify
- The week gets drafted in place
- A role decides who can approve
- The client sees their own account only
By hand
What it costs you today.
Captions pasted into email or a shared document, then re-pasted back with edits
Approval that arrives as a message rather than as a decision attached to the post
No record of who approved what, which becomes a problem exactly once
An example from the demo world
What it looks like on a real week.
A carousel for a client is finished on Tuesday. It is sent for approval as a private link the client opens without an account, and they answer approve or ask for a change on the post itself.
Nothing publishes until that answer comes back, and the post shows its state, waiting, approved or changes asked, so nobody has to remember who was chased and when.
In Synclify
How it runs instead.
- 01The week gets drafted in placePosts, captions and times sit on the calendar as drafts rather than in a document that has to be transcribed back.
- 02A role decides who can approvePeople have roles inside a workspace. Drafting and publishing are separate permissions, so the person who writes is not necessarily the person who can send.
- 03The client sees their own account onlyA client signing in reaches their workspace and nothing else on your book, including any indication of who else is on it.
- 04Publishing waits for the tapAnything that leaves the building waits for a confirmation, and that confirmation expires after 24 hours rather than sitting open indefinitely.
Your clients cannot see each other.
There are 400 tools, too many to check by reading the code, so we test them. Each client account gets a made-up word that appears nowhere else. We then run every read that needs no extra input as eight different people, and search every answer for those words. If one client's word turns up in another client's answer, the test fails.
- a creator: not found in any answer
- a brand: not found in any answer
- the agency: not found in any answer
- a client of theirs: not found in any answer
- a second client: not found in any answer
- an unmanaged workspace: not found in any answer
- the creator's team member: not found in any answer
- the agency's team member: not found in any answer
- control · 15 readsThe control found nothing, so the test itself is broken and this run does not count.
Only the words belonging to a creator turned up in the answers. The other 7 accounts had none of theirs.
A tool that quietly returns nothing looks exactly like a tool that correctly refused, so the test also forces every tool to fail loudly.
The control account is the one where the word is supposed to appear. If the control finds nothing, the test itself is broken and the run does not count.
Reading the code is not enough to catch this kind of mistake, and it has been missed before. That is why this is a test and not a promise.
An automated test fills a separate copy of the database with one agency's two clients and an account it does not manage, runs every argument-free read as each of eight people, and then searches every answer for the words that belong to somebody else.
How we checked this
Where it stops
Approval is a permission inside the product, not a legal signature. It records that a person with the right role approved a post, which is what a disagreement about scope usually needs.
Stop doing it by hand. Ask for it instead.
Connect an account and type what you want. Every plan is the whole product.
Cancel any time. Every dashboard and report is free to open.