Share links
Send a link, not a PDF export. Your client comments on the real calendar.
Client sign-off usually degrades into a spreadsheet emailed back and forth, because giving a client a seat in your tool is worse. A share link is the middle path: they see the calendar, they comment on posts, they approve — and they never create an account.
Revocable, and scoped to one workspace.
How it works
Client approval calendar, step by step.
- 1
Create the link
One per client or per engagement, from the workspace it belongs to.
- 2
Name the reviewers
Add the people who should be able to comment, so feedback is attributed.
- 3
Send it
They open it in a browser. No account, no password, no seat.
- 4
Revoke when done
Revocation is immediate and does not disturb your other links.
Capabilities
What you get with Client approval calendar.
- No account for the client
- The link itself carries the access. A client reviewing one calendar a month should not have to keep a password for your tooling, and a seat you pay for is the wrong shape for that relationship.
- Named recipients
- Add reviewers to a link so comments arrive attributed rather than anonymous. "Someone said move this to Thursday" is not actionable feedback.
- Comments land on the post
- External comments go onto the post itself, in the same thread your team uses. There is no separate client inbox to reconcile against your internal notes.
- Revocable, one link at a time
- Revoke a single link when an engagement ends and every other link keeps working. The token is the credential, so revoking it closes the door immediately.
Why a link instead of a seat
Three options exist for client review and two of them are bad.
Export a PDF or a spreadsheet. Feedback comes back detached from the post, and someone re-types it. Every round adds a chance to lose a correction.
Give the client a login. Now they are a member of your workspace, you are managing their password resets, and they can see machinery that is not their business.
Send a link. They see the calendar as it actually is, comment where the comment belongs, and hold nothing you have to administer.
What the client sees
The calendar for that workspace, with posts as they are currently planned — including dated drafts, which is what makes this useful before anything is committed. They can read and comment. They cannot connect channels, change your schedule, or reach billing.
Comments they leave arrive on the post, in the same thread your team is already using. So there is no second stream of feedback to merge.
Name your reviewers on the link. Attributed feedback is worth much more than anonymous feedback when two people at the client disagree with each other.
The token is the credential
A share link carries its token in the URL. That is a deliberate design decision rather than a convenience: because the token is part of the path, it is validated as a typed field before any handler runs, rather than being read out of a request body somewhere deeper.
The practical consequences:
- Anyone with the link can open it. Treat it like a password.
- Revoking is immediate.
- A link is bound to one workspace and cannot be made to show another.
One link per engagement
Create a link per client rather than reusing one. It costs nothing, and it means the end of an engagement is a single revocation instead of a question about who else was on the old link.
For internal sign-off among people who do have accounts, use the review flow instead — it records explicit approve, reject, and request-changes decisions with history.
Found this useful? Pass it on.
Questions
Frequently asked questions Everything the first evaluation usually needs.
- Does my client need a Postonus account?
No. They open the share link in a browser and can read the calendar and comment on posts without signing up or being invited as a member.
- Can a client approve a post through the link?
They can comment on the posts they are shown, which is how sign-off usually works in practice. Formal approve, reject, and request-changes decisions are made by workspace members in the review flow.
- How do I stop a client seeing the calendar later?
Revoke the link. It takes effect immediately, and it only affects that link — other clients’ links are untouched.
- Can one link see more than one workspace?
No. A share link belongs to the workspace that created it, and it can only ever show that workspace’s posts. An agency creates one link per client workspace.
- Is the link private?
Anyone holding the link can open it, so treat it as a credential — that is exactly why revoking is one click. Naming recipients also tells you who is expected to be using it.
- Can I share a single post rather than the whole calendar?
Yes. A single post can be shared on its own link for feedback, which suits the "just look at this one thing" case without exposing the rest of the plan.
Keep reading
- Team collaborationInvite teammates with owner, admin, or member roles, leave threaded comments on a draft, and route posts through approve, reject, or request-changes first.Read
- Queue & reliabilityA queue that flags a post at risk before its publish time, refuses to send something an hour late, and turns a crashed worker into a retryable failure.Read
- Auto-repurposePoint a Growth Autopilot at a platform you already win on and a channel you want to grow. Postonus mines your top posts and drips reshaped drafts in for review.Read