Nothing goes out without your OK.

Every path that can publish has a stop where a person decides. Team posts can wait for an admin. The FoPost Agent proposes and you approve. Workflows hold what they generate, campaigns are approved as a batch, and replies drafted for your inbox wait until someone sends them. Afterwards the activity log shows what happened and who did it.

Team posts held until an owner or admin approves them
The FoPost Agent proposes anything that reaches a network
New workflows hold their posts for approval
An activity log of who did what
The cost of publishing with nobody checking

One wrong post is a long week.

A new teammate scheduled a client post with last year’s prices, and nobody saw it until the client did.

You tried an AI tool that could post for you, then turned it off because you could not see what it was about to do.

Something was published on Friday night and on Monday nobody could say who sent it, or from where.

Is this for you?

Who needs approvals?

For you if

  • Agencies whose junior staff write posts that a lead should see first
  • Teams that want an AI to draft and act, but only with a person’s yes
  • Brands where one wrong reply in public costs more than a slow one
  • Anyone who needs to answer “who posted this?” a week later

Not for you if

  • You need a chain of reviewers, such as a writer, then legal, then the client. One approval releases a post.
  • You want clients outside your team to approve posts. Post approvers are the brand’s owners and admins.
What's inside

A stop before every send.

Posts, agent actions, workflows, campaigns and replies each have their own approval, set to hold by default where it matters.

Post approvals for your team

Turn on Require Approval for a brand and posts scheduled by members and editors wait in the Approvals tab under Posts. Owners and admins approve them. A rejection needs a reason, sends the post back to drafts, and tells its author why.

The agent proposes, you decide

Publishing, retrying, unpublishing, editing a live post, liking, replying, messaging, sending a broadcast and pausing an ad are all proposals. The FoPost Agent shows what approving would do and waits. The same rule holds when you use it from another AI app over MCP.

Workflows hold their posts

Require approval is on for every new workflow, so the posts it generates wait in the approvals queue instead of going out. Turn it off for a workflow you trust to post on its own.

Campaigns approved as a batch

A campaign’s posts stay drafts until you choose Approve all or approve only the ones you select. Reject removes the drafts and never touches a post that is already live.

Replies checked before they send

Replies drafted by a workflow or by the agent wait in the inbox’s Approvals tab. Edit the text, send it, or reject it. A workflow’s Send Message step holds its replies by default.

An activity log

Settings → Activity lists what happened in a brand: publishes, account connections and health, webhook deliveries, inbox replies, automation runs, billing and security. Each entry names who did it: a person, an API key, the agent, or the system.

How it works

How the approvals fit together

01

Decide what is held

Switch on Require Approval for a brand that needs review. Workflows and the agent hold their work without any setup.

02

Work as usual

Teammates schedule posts, workflows generate them, and the FoPost Agent drafts and proposes. Held work never reaches a network.

03

Approve or reject

Reviewers see held posts in the Approvals tab under Posts, held replies in the inbox’s Approvals tab, and agent proposals as a card in the chat.

04

Check the record

Settings → Activity shows what was published, sent and changed, and who did it, for the last 90 days.

vs the alternatives

Why this beats “send it to me first”.

Three ways teams keep a check on what gets published. Only one keeps the check inside the tool that publishes.

Screenshots in a chat thread

What most teams do

  • Drafts pasted into chat for someone to look at.
  • The approved version and the posted version drift apart.
  • No record of who approved what.

An AI tool with posting rights

What fast-moving teams try

  • It acts the moment you ask.
  • You find out what it did after it did it.
  • Turning it off is the only safety switch.
FoPost

FoPost approvals

What you actually want

  • Held posts wait in the tool that publishes them.
  • Agent actions wait for a person.
  • Workflow posts and replies held by default.
  • An activity log of who did what.

Publishes to all major networks

Frequently asked questions

Who can approve a held post?

The brand’s owners and admins. Members and editors can write and schedule, but their posts wait while Require Approval is on. Posts scheduled by an owner or admin are not held.

Can the agent publish without asking?

No. Anything the FoPost Agent does that reaches a network is saved as a proposal and only runs when a person approves it. Saving a draft and reading your data need no approval, and moving an already scheduled post to a later time applies straight away.

Does the same rule apply over MCP?

Yes. An AI app connected over MCP uses the same tools as the FoPost Agent, so it proposes in the same way and the proposal waits for you.

Can a workflow post on its own?

Only if you let it. Require approval is on for every new workflow, including the ones the agent builds, and the posts a workflow generates wait in the approvals queue until you turn that off.

Can I change a reply before it is sent?

Yes. In the inbox’s Approvals tab you can edit a held reply, then send it or reject it.

What happens when I reject a post?

You give a reason, the post goes back to drafts, and its author is told why so they can fix it and send it again.

What does the activity log record?

Publishes, account connections and health changes, webhook deliveries, inbox replies, automation runs, billing and security events, each with who did it. Filter by kind, and look back up to 90 days.

How does the agent know what to say?

From your brand voice and your knowledge base. Settings → Knowledge holds your own answers, notes, pages and files, and the FoPost Agent quotes them when it drafts a reply instead of guessing. Only sources marked Ready are used.