
A useful approval process answers a concrete question: who may turn this version of a post into a public send? “The client saw the calendar” is too vague. They may have reviewed an older caption, missed the attachment, or assumed the date was still a suggestion.
Postbean currently has a coming-soon placeholder in its Approvals tab. It does not provide a completed native approval workflow there. You can use drafts, permissions, and scheduling as parts of a manual process, but you should not describe that arrangement as an enforced approval gate.
If your organization requires a system-enforced sign-off, choose a process and software that provide it today. The method below explains what to define, and how a team using Postbean can keep manual review separate from the action that releases content.
Define the object being approved
Approval should cover a particular caption, asset set, destination list, and release plan. Reviewing only the text leaves open whether the image, account, or date is acceptable. A correct announcement can still be harmful if it goes to the wrong business account.
Create a review packet in your existing collaboration system. Include the saved post ID, the final copy for each destination, attached media, intended accounts, and proposed time zone. Add the source for any claim that needs checking.
Call this a team procedure rather than a Postbean feature. The important result is that a reviewer can identify what they are authorizing without searching several chats for the latest screenshot.
Separate editorial review from release permission
Someone can be responsible for checking content without needing administrative control over the workspace. Someone else may be responsible for scheduling approved posts. Define those responsibilities before distributing credentials.
Postbean’s permission model defines owner, admin, and member, but the panel does not currently offer a member invitation flow. Post permissions also consider authorship and workspace management. These are product permissions, not a full set of reviewer states such as “legal approved” or “client changes requested.”
For API integrations, drafts:write is separate from posts:publish and posts:delete. Use narrow credentials, but inspect all actions your workflow permits. Scheduling authorizes a future public send; a missing immediate-publication scope is not enough to prove that nothing can leave the workspace.
Make the review request specific
“Thoughts?” invites a conversation without defining a decision. Ask for a bounded response: approve this version for these destinations and this date, or identify the changes that block release.
Set a review deadline with the actual publication plan in mind. If the reviewer misses it, leave the content unapproved or move the date according to your agreed policy. Do not treat silence as approval unless your organization has explicitly adopted and accepted that rule.
Use one place for the decision. Feedback can arrive through several channels, but someone should consolidate the resulting version and confirm which comments were applied. Otherwise, the operator scheduling the post may see one person’s approval and miss another person’s unresolved correction.
Establish which edits invalidate approval
An approval loses meaning if the content changes freely afterward. Define the edits that require another review: a changed price, a new claim, another target account, a replacement photo, or a different release date may all matter.
Your team can decide whether a typographical correction needs renewed approval. Make that rule clear rather than have every operator improvise. Record the final version after small edits so the release packet still matches what will be sent.
Keep one saved post through revisions where possible. Postbean’s update_post edits an existing post; creating another draft produces another ID. If your external approval record refers to the old ID, a newly created draft has not automatically inherited its sign-off.
Give AI a preparation role with a clear stopping point
An assistant can assemble source facts, suggest captions, or save drafts. State the stopping point directly: “Save as draft, return the post ID, and do not schedule or publish.” Then read the stored object back to check that it matches the request.
On hosted Postbean MCP, create_post_draft always creates drafts. The local @postbean/mcp package exposes create_post; pass draft: true explicitly because omitting draft and schedule can request immediate publication. Tool names and defaults deserve review alongside the prompt.
If the assistant calls Postbean’s AI-generation tools, those operations consume credits. Decide who may authorize that usage separately from who approves the final copy. Generating another variation is not evidence that a person has accepted the previous one.
Run a factual check before asking for taste feedback
First verify dates, offer conditions, and links against their sources. A reviewer should not have to choose a favorite opening while the price is still unknown. Mark missing information clearly rather than let the writer complete it with plausible wording.
Then review voice and clarity. Remove claims the organization cannot support, including invented customer reactions or urgency. For network-specific versions, check that an adaptation did not remove an important condition.
Postbean exposes text-limit problems through publish_issues and checks them before scheduling or publication. This technical validation does not decide whether a claim is true or a customer has consented to a photo. Those remain review responsibilities.
Authorize scheduling explicitly
Once the version is approved, have the designated operator set its schedule. Read the saved result back and compare destination accounts and time against the approval packet.
On hosted MCP, get_workspace returns the workspace zone and local clock. A timestamp without an offset uses that zone; one with an offset or Z identifies an exact instant. Include the zone in the review request so “09:00” has an agreed meaning.
If different networks have different dates, review those dates individually. Postbean supports per-network schedules, which means one post can remain scheduled after another destination has already published. A single overall date may not describe the whole release plan.
Have a rule for late changes and cancellation
Decide who can stop a scheduled post when a fact changes. In Postbean, cancelling a schedule and publishing immediately are separate actions. A cancellation request should identify the saved post rather than say “stop the announcement” when several drafts share a similar title.
After cancellation, inspect the result. If a destination has already published, stopping future work does not erase that publication from the network. Your team needs a response for content that is already public, separate from the rule for pending content.
For urgent corrections, keep a short decision record: what changed, who authorized the action, and which destinations were affected. This record belongs to your incident procedure; do not assume it appears automatically in a native approval history.
Close review with a publication check
At the intended time, inspect the outcome per account. A post may be queued, published, partially published, or failed. The fact that an operator saved a schedule correctly does not establish that every network accepted the content.
Route failures to someone who can act. A missing platform option may require a content decision; an account authorization problem may require the account owner. Do not automatically recreate the entire post when one destination needs attention.
Keep the approval packet attached to its post ID until the release is settled. That makes a later question answerable: this was the version reviewed, these were its targets, and this is what happened. The agency workspace guide covers client separation, while the automation guide explains how to keep draft preparation apart from an automated release branch.
Sources
- Postbean API permissions — checked November 22, 2026
- Postbean agent instructions — checked November 22, 2026