Updated
AI agents for every client, with approvals per client
An agency can give each client its own Postgale workspace, so each client’s accounts, keys, approvals and audit log stay separate and a key for one brand cannot touch another. Agents draft and schedule through the MCP server or REST API, approval is required per client workspace, per account or per agent key, and the team approves, edits or rejects in the dashboard. Links that let clients approve from their phone are in early access.
How does an agency use Postgale?
Postgale is the secure layer for AI agents on social media. For agencies that already draft with AI, it turns “the agent wrote it” into a controlled step: the agent proposes, a person signs off, and every action is recorded.
| Need | How it works today |
|---|---|
| Keep clients apart | A workspace per client. API keys and signed-in apps belong to one workspace and act only there. |
| Approve before it goes out | Require approval for the client’s workspace, for single accounts, or for the key a given agent uses. Posts, comment replies, DMs and edits to live posts wait in Dashboard → Approvals. |
| Edit instead of reject | A reviewer can edit the text of a queued item; it then runs with their text. Approval is bound to the exact content, so a later edit needs a new approval. |
| Know who did what | The audit log records each write with the key or app that made it, and who approved queued actions. |
| Track by client in your own tools | Set a customer reference (externalId) on each account and register webhooks for post.* and action.* events. |
How do I set it up for a client?
- Create a workspace for the client and connect its accounts under Dashboard → Accounts. The account owner signs in on the platform’s own page, or the agent sends them the link from
connect_account. - Turn on approval for the workspace (or only for the accounts that need it).
- Create one API key per agent or workflow under Dashboard → API keys, or connect ChatGPT or Claude with a sign-in and tick “Hold posts from this app for approval”.
- Point the agent at the client’s brief and ask for drafts and scheduled posts; review them in Approvals.
Ask your agent“For the Northline workspace: draft next week’s five Instagram posts and matching Threads posts from the brief in this folder, schedule them for 9am on weekdays, and tell me when they are waiting for approval.”
Can my clients approve posts themselves?
Today, approvals happen in the Postgale dashboard, by members of the workspace. Client approval links, which let a client approve next week’s posts from their phone without an account, are in early access, together with rules per client and a weekly report to forward.
What is available today, and what is in early access?
Available today: publishing and scheduling on Instagram, Facebook Pages, Threads, TikTok, Bluesky and Mastodon; comments on Instagram, Facebook and Threads; direct messages on Instagram, Messenger and WhatsApp; analytics; approval per workspace, account, API key or connected app, with one review queue for posts, replies, messages, moderation and edits to live posts; the audit log; revocable access; the REST API, the MCP server and signed webhooks. X, Telegram and Discord, Reddit and ads are coming soon.
In early access, not generally available: rules checked before every action (so safe actions go through and only risky ones wait), approvals from your phone, client approval links, shadow mode, pause and undo, fine-grained permissions per agent, and a weekly report per client.
Common questions
Yes, with one key or sign-in per client workspace. Each key acts only in its own workspace, so a mistake cannot cross from one brand to another.
Not yet generally: client approval links are in early access. Today, members of the workspace approve in the dashboard.
Instagram, Facebook Pages, Threads, TikTok, Bluesky and Mastodon for publishing, and WhatsApp Business for messaging. X, Telegram and Discord, Reddit and ads are coming soon.