Social Media Scheduler for Agencies, One Client Workspace at a Time

Delegate Publishing, Keep the Client Decision

Keep your creative review, project management and client reporting tools where they already work. Start with a client whose finished-video workflow and destination settings fit the publishing path you choose.

Why Choose an Agent-Controlled Publishing Workflow?

Postdom is worth evaluating when your agency already uses an AI agent or is building a repeatable publishing process. The benefit to test is delegated execution with clear human decisions—not a lower-cost bundle of calendars and client reports.

• Keep a client’s publishing access separate. Authorize the agent for that workspace and verify its returned accounts before it submits.
• Review the request that will be sent. In Post review mode, a human checks the content, targets and timing before provider handoff. The agent cannot approve itself.
• Know which destinations need attention. Follow the same post ID and preserve each destination’s success or error instead of calling a partly published post complete.

If your main requirement is a no-login client portal, creative production or ready-made branded reports, keep those tools. Use the first-workspace trial to decide whether controlled agent publishing adds enough value to your existing stack.

What Does Postdom Cost for an Agency?

Price each client workspace for the accounts, people and monthly publishing volume it needs. A workspace is the billing unit; it is not a free container inside one agency-wide subscription.

USD per workspace per month with monthly billing. Paid self-serve plans charge $0.20 per successful destination-publish above that workspace’s allowance. One post successfully published to three destinations uses three units. Free blocks at its cap. Examples exclude taxes, publishing overages, external model charges and Postdom Chat AI-action overage. Your own agent does not spend Postdom Chat’s AI allowance. Annual billing and Platform terms differ.

Seats include members and pending invitations. Separate people need separate seats. Free’s one-seat allowance blocks adding another person when occupied. Existing members remain after a downgrade; the lower limit blocks new invitations.

New workspaces start with a 14-day complimentary Growth trial without a card. Without a paid subscription or another qualifying entitlement, the workspace falls back to Free after that trial. The trial does not raise the owner’s workspace-creation ceiling. Test the review workflow in one workspace before budgeting for several clients.

Worked Examples: Three Client Workspaces

Workspace creation is a separate owner-level allowance: Free and Starter permit creation up to 1 owned workspace; an eligible paid Growth subscription raises the creation ceiling to 3; Scale to 25. The best qualifying plan among your owned workspaces sets that ceiling. A complimentary Growth trial alone does not raise it. Existing workspaces are retained after a downgrade; the cap blocks additional creation. Creating a workspace does not include another paid subscription.

Compare Current Plans and Billing Terms

How This Social Media Scheduler for Agencies Handles Client Work

1. Choose the Client Workspace

   Open New workspace… from the workspace menu, Cmd+K, or the switcher to create a client workspace, or open the workspace menu to move to an existing one. Cmd+K marks the current workspace Current. Keep that client’s connected accounts, brief, agent access and billing there; switching the dashboard does not switch a separately configured agent connection.

2. Connect the Right People and Accounts

   Open Agents to authorize the agent for this workspace. Separately, have an authorized human connect the client’s profiles in Social accounts. Owners and admins can invite collaborators from Invite people. Choose their role deliberately: membership is not permission to change every approval or policy control.

3. Save the Brief and Name the Reviewer

   In Workspace settings, open Rules and edit Voice & content with the client’s voice, approved claims and things to avoid. Rules also contains How much, and when for enforced limits. The brief guides the agent but is not an approval. Name the person who will review the actual video, caption, audience and planned time.

4. Choose When a Human Must Approve

   For review of every agent post, set that account to L1 Post review before submission. Do not assume it is the default. Choose plan review only when a human is ready to approve the accounts, time window and scope; bounded autonomy uses the account’s saved policy instead.

5. Submit the Finished Video, Then Follow Its ID

   Give the agent an accepted video URL or already-stored media handle, the selected account IDs, the reviewed caption and a future UTC time. Keep the returned post ID. If review is required, an authorized human checks the exact request in Review. Then use Schedule and the run result to distinguish waiting, publishing and published.

Client separation is a habit as well as an access boundary. A workspace credential scopes API requests; it does not clear the agent’s memory or choose the correct connection. Start a separate task for each client and verify the workspace, brief and accounts before submitting.

Workspace settings · Accounts and agent access · Policy and Workspace Brief · How human authority works

How Do Clients and Teammates Approve Posts?

Agree who is responsible for client sign-off and who records the decision in Postdom. They may be the same person, but an email approval and a Postdom approval are different steps.

For a client who expects to sign off every post, use L1 Post review before submission. Do not assume new accounts start there. An agent cannot approve its own work or increase its authority. Invite reviewers with an appropriate role. Admin access is not a narrow client-review permission.

Workspace owners, admins and members can review posts. Plan approval requires an owner or admin. Clients need their own signed-in workspace membership; there is no no-login guest approval portal, named-reviewer assignment or sequential approval chain in this verified workflow.

Actual product interface, not a customer workspace. Willow Studio and its post are synthetic test data; the gray video is a test asset. No approval or publication was completed. This fixture requests immediate publishing, while your client workflow can specify a future time. Not recorded disclosure fields require a human check, not an assumption.

When a reviewer requests changes, feedback does not automatically revise the post. Prepare corrected content as a new draft, submit it under the intended review mode and check that the replacement is awaiting approval. Keep the author and reviewer coordinated. See the Full Approval and Correction Workflow.

A Client Handoff You Can Use

Imagine Harbor, a fictional client, has approved a launch video. Your agency lead opens Harbor’s workspace, confirms its Instagram account and current brief, and asks the agent to submit the reviewed video for the agreed UTC time. The account is set to Post review.

The returned post needs approval. The lead opens Review, checks the video, caption, audience and disclosures, then records the decision. In Schedule, they check the saved time and status. After handoff, the agent reads the same ID and reports the actual Instagram result, not just “submitted.” If anything fails, the lead owns the next decision.

Before moving to Cedar, another fictional client, stop Harbor’s task. Choose Cedar’s connection and read Cedar’s brief and accounts again. Switching the browser workspace alone is not enough.

• Confirm the client workspace and the connection authorized for it.
• Read its current brief and select its returned account IDs.
• Preview the finished video and confirm caption, audience and disclosures.
• Record the human reviewer, review mode and intended UTC time.
• Keep the post ID, each destination outcome and any unresolved action.

Client / workspace: [name and verified workspace reference]
Agent connection: [connection authorized for this workspace; never paste a key]
Accounts: [returned providerAccountIds and destinations]
Brief: [current version read from this workspace]
Finished video: [accepted URL or stored handle reviewed by a human]
Caption, audience and disclosures: [exact reviewed settings]
Reviewer and authority: [person, account review mode, approved plan if required]
Schedule: [future UTC time; record the client’s local time and date-specific offset separately]
Post ID: [returned after submission; do not invent one]
Outcome: [each destination’s exact result and error, if any]
Next action / owner: [review, wait, reconcile or a human recovery decision]

Check the Agent’s Settings Before a Client Launch

Test whether the publishing path supports the client’s required format, audience and disclosures with one client before connecting the rest. These implementation notes describe convenience helpers, not every capability of the current HTTP API.

Work only in the explicitly selected client workspace and configured connection. Do not reveal credentials.
Read get_workspace_status, list_accounts and get_brief. Confirm the workspace reference, current brief and providerAccountIds with me. Stop on a mismatch, pause, locked connection or unclear policy. Do not reuse another client’s context or IDs.
Use only the finished video I supply. Show me the video, caption, selected accounts, audience/disclosure settings and future UTC time before submission. Do not generate replacement media.
Use a released helper only if its actual settings fit: TikTok is private with AI and preview/consent assertions, Instagram asserts AI generation without a private override, and YouTube is private with synthetic-media disclosure and not-made-for-kids. LinkedIn receives no settings: Postdom’s publishing provider chooses the required visibility value, which this helper does not expose, and it carries no AI disclosure. Treat LinkedIn as a destination where audience and disclosure are unavailable controls, and stop rather than assume them. Facebook is sent the default Reel setting when no surface override is supplied, and carries no AI disclosure on the publishing path. X and Snapchat are sent no destination settings; the current Snapchat transport publishes to Stories and does not offer Spotlight, and neither carries an AI disclosure; Snapchat also requires a Public Profile on the account, so a client account without one cannot publish. Threads is sent nothing either and carries no AI disclosure; a Threads profile being public or private is what decides the audience, and the post inherits it from the account. Bluesky is sent nothing either, and there it is because the post record has no visibility field at all - every Bluesky post is public, which is a fact about Bluesky rather than about Postdom. Treat all five the same way as LinkedIn: audience and disclosure are not controls you have here. Stop if any assertion is wrong or a required control is unavailable.
I decide approval mode and policy. Submit only after my review and permission; include plan_id only for work inside a human-approved plan. Never approve yourself or widen authority.
Save the returned post ID and read get_publish for that same ID. Stop for required human review. Wait for scheduled/publishing only within an agreed waiting budget, then return the ID if unresolved. Preserve each destination result. Reconcile an uncertain submission before retrying; do not replay successful destinations.
Before another client, stop this task and verify that client’s connection, accounts and brief again.

When a Client Post Needs Attention

Return the post ID, destination, current state and error to the named owner. Do not hide a missed slot behind a new submission.

Close the Loop With Evidence the Client Can Understand

Separate “published” from “performed well.” Save each destination outcome, then read available performance data for that client. A missing, delayed or unsupported metric is not zero. Keep its availability and reason when you prepare the client report; do not combine unlike platform metrics into an invented total.

Use the current brief, post results and available measurements to propose the next plan. Your team still supplies the interpretation and the client-facing report. These records do not prove revenue attribution or client growth. Read how measurement availability works.

Before quoting the engagement, check current workspace pricing and the client-facing features you need. Workspace switching does not imply a consolidated portfolio report or no-login client portal. Confirm branding and custom-domain access before including them in a proposal.

Agency Questions