Manual
Every publish stays with a human.The agent creates a draft. A human chooses whether and when it publishes.
Human authority
Social Media Approval Software That Keeps Humans in Control
Postdom is social media approval software for teams that delegate publishing to agents. Choose manual control, per-post review, approved plans or bounded autonomy. Reviewers sign in to the workspace; humans keep approvals, policy changes, pauses and exceptions.
The agent cannot approve itself, expand trust, or resume paused activity.
Approve the planReview the boundary instead of every post.
Posts flow only inside one approved plan covering the accounts, UTC window, and post maximum.
Per-post review
Review the Version That Will Publish
Choose L1 when each post needs a human decision. The workflow below describes the product’s checks; it is not a live approval control.
- 01
Prepare the Post
Connect the intended accounts and choose L1 Post review when a human should approve each post. The agent prepares the content and returns work that needs approval to a human.
- 02
Review the Exact Version
Sign in to the workspace and check the content, destination accounts and intended time. Approval checks the version and request fingerprint; a stale review cannot approve changed content. Approval can authorize publishing now or at the scheduled time.
- 03
Follow Each Destination
An approved or scheduled post is not yet a successful publication. Read the run and each destination’s outcome. If one destination fails, preserve the successful results and inspect the error before taking another action.
Observed product evidence
See an Existing Publishing Run
The run separates authorization from destination delivery. Use the destination result to understand what happened after work was permitted.
This is a real run record, not a customer case study or a complete per-post review demonstration. It does not show a request-changes and reapproval sequence, identify the authority mode, or independently verify the post’s public visibility. No new post was approved or published to capture this image.
Human decisions
When Review Cannot Proceed
Changed content, pauses and missed times need a clear next action. They are not publication successes.
- 01
The Content Changed
Postdom refuses a stale version or request fingerprint. Reopen the current post and review that version before approving it.
- 02
Activity Is Paused
A paused target account or workspace-wide agent pause prevents approval from proceeding. A human must decide whether to resume; the agent cannot unpause itself.
- 03
The Approval Deadline Passed
If the scheduled time passes before approval, the post requires an explicit decision to publish now or reschedule. It is not silently treated as an on-time publication.
Authority modes
How Postdom’s Social Media Approval Software Works
Each connected account has one human-selected authority level. Move from manual control to bounded autonomy without giving the agent permission to promote itself.
Post review
Nothing publishes without a post decision.Each agent post waits for exact human approval before provider handoff.
Plan review
Review the boundary instead of every post.Posts flow only inside one approved plan covering the accounts, UTC window, and post maximum.
Bounded autonomy
Routine work runs inside saved account limits.Posts flow only inside the account's saved daily cap, visibility allowlist, and quiet hours.
Account boundaries
Routine work stays inside the lines.
L3 evaluates the saved account policy before work can flow. L2 evaluates the approved plan instead.
Current new-account default: up to 3 posts per local day, with quiet hours from 23:00 to 07:00. Humans can edit these values or select a stricter mode.
Daily cap3 / local day
VisibilityAllowed values only
Quiet hours23:00–07:00 · account timezone
AccountsSelected destinations
WindowUTC start and end
CapacityApproved post maximum
Strictest policy
One request gets one boundary.
When selected accounts use different modes, Postdom applies the strictest level to the entire request. It does not split one post into partially authorized publishes.
Read scheduling authorityTikTokL3Bounded autonomy
Instagram ReelsL2Plan review
YouTube ShortsL3Bounded autonomy
Human authority
Authority stays human.
The agent can prepare work and start a connection handoff. A human completes provider authorization and keeps every control that changes authority.
Pause controls
Stop one account or all agent work.
An account pause blocks execution for that destination. The workspace-wide pause blocks agent write activity across the workspace. Only a human can resume either one.
Blocks execution for this destination.
Returns control to a human across the workspace.
Plan authority
Approve the boundary, not every click.
At L2, the agent proposes the accounts, UTC window, objective, and maximum number of posts. A human approves that bounded plan once; eligible posts then flow inside it.
- 01
Proposes
Accounts · UTC window · objective · maximum posts
- 02
Approves
Approve · request changes · reject · let expire
- 03
Enforces
Only eligible posts inside the approved boundary
Agent-readable policy
Return the boundary exactly.
Agents read account policy before submitting work. Approval, policy, trust, pause, and exception states return to a human with the exact resource ID.
This page has a raw Markdown twin. The exact callable contract remains in the connected tool schemas and authority documentation.
Policy FAQ
Authority questions.
Who can approve plans and change account rules?01
Workspace owners and admins can approve plans, change account policies and resume paused activity. Agent credentials cannot perform these human-only actions. Reviewers must use their own signed-in workspace access.
Can a client approve without signing in?02
Reviewers sign in to the Postdom workspace. This is not a no-login guest approval portal. Plan workspace membership and the required human permissions before inviting a client into your process.
Which plan fits a reviewer and a publisher?03
Free includes 1 workspace seat. Starter includes 2, and Growth includes 10. Choose a plan that accommodates the people who need workspace access; seat allowances include pending invitations. Check current pricing and account allowances before choosing.
Can an AI agent approve its own plan?04
No. Agent credentials cannot exercise human approval routes, expand trust, change account policy, or approve their own work. The agent returns the exact plan or post state to a human.
Can I approve a plan instead of reviewing every post?05
Yes. At L2 Plan review, a human approves one bounded plan covering selected accounts, a UTC window, and a post maximum. Eligible posts can then flow only inside that approved boundary.
What happens when connected accounts have different authority levels?06
Postdom applies the strictest selected-account level to the entire request. It does not split one post into separately authorized and unauthorized publishes.
How do quiet hours work?07
At L3 Bounded autonomy, Postdom checks the account's saved quiet-hours window in that account's timezone before authorizing work. A human can edit the policy or choose a stricter authority mode.
How do I stop agent activity?08
A human can pause one connected account or activate the workspace-wide agent pause. Paused destinations block execution, the global pause blocks agent writes, and only a human can resume activity.
Does the agent handle my social-account password?09
No. The agent may create an authorization URL, but a human completes the provider's authorization flow. The agent does not receive or enter the provider password.
Bounded operation
Give the agent room to work.
Choose the review point, keep authority human-owned, and let permitted work move without another click.
Create a workspace