OWNER
Full control of the workspace — approves, publishes, manages members and billing.
✅ Review before reach
A social media approval workflow nothing gets around
An approval workflow that lives in a Slack thread is a wish, not a workflow. In Nimply, approval is a status in the post’s own pipeline — every draft, whether a teammate wrote it or an AI agent did, waits at the gate until someone with the right role signs off.
DRAFT
Editors, Admins, Owners — and AI agents
Anyone (or any agent) writes. Nothing here can reach a feed.
PENDING_APPROVAL
Gate: Admins & Owners approve
The post waits. Approve it forward or send it back with changes.
SCHEDULED
Locked to the calendar
Signed off and slotted. Publishes automatically at its time.
PUBLISHED
Live on your channels
On the record — with a review trail behind every single post.
The AI angle
Approval matters more now, not less
When only humans wrote your posts, review was mostly about typos and tone. Now AI can draft a week of content in a minute — which means the bottleneck isn’t writing anymore, it’s judgment. The teams that win with AI aren’t the ones that let it run loose; they’re the ones with rails.
Nimply’s rail is simple: agents follow the exact same pipeline humans do. An agent can draft a carousel, a reply, or a repurposed post — but it files a DRAFT like everyone else, and a human approves it into the schedule. Agents never publish directly. One pipeline, no side doors, regardless of who — or what — did the writing.
Who does what
Four roles, one clear gate
Workspace roles decide who can draft, who can approve, and who just watches. The person who writes isn’t automatically the person who ships.
ADMIN
Runs the day-to-day: approves pending drafts, manages channels and the calendar.
EDITOR
Creates and edits content, submits drafts for approval. Can't push past the gate.
VIEWER
Read-only. Sees the calendar and post statuses — ideal for stakeholders and reviewers-in-spirit.
The stakes
Brand safety is a system property
A bad post is rarely one person’s failure — it’s a process that let one person’s Tuesday afternoon reach the whole audience unreviewed. Policies and good intentions don’t scale; a pipeline where unreviewed content structurally cannot publish does. That’s the difference between asking people to be careful and making carelessness impossible.
For regulated teams the gate isn’t optional at all. If you’re publishing as a law firm or a financial advisor, compliance review before publication is table stakes — and a status pipeline gives you a workflow where that review is a recorded step, not a memory.
Running social for clients? The same pipeline powers client approvals — invite the client into their workspace and let them hold the gate themselves.
Approval workflow — FAQ
How does the approval workflow actually work?
Every post moves through four statuses: DRAFT, PENDING_APPROVAL, SCHEDULED, and PUBLISHED. A draft — written by a teammate or filed by an AI agent — is submitted for approval, waits in the pending state until someone with approval rights signs off, and only then lands on the schedule. Publishing happens from SCHEDULED, never straight from a draft.
Who can approve posts?
Approval follows workspace roles. Every member is an OWNER, ADMIN, EDITOR, or VIEWER: Editors create and submit drafts, approval rights sit with Admins and Owners, and Viewers get read-only visibility. That separation — the person who drafts isn't automatically the person who ships — is the whole point of a review gate.
Do AI agents go through the same review?
Yes, and this is non-negotiable in Nimply's design: agents never publish directly. Whatever an agent drafts — replies, carousels, repurposed posts — it lands as a draft and waits for human sign-off exactly like a teammate's work. The rails don't care whether the author has a pulse.
Can I skip approval for trusted team members?
Members with approval rights (Admins and Owners) can move their own work forward, so a solo founder or a senior marketer isn't stuck approving themselves through busywork. For everyone else, the gate holds — that's what makes it a workflow instead of a suggestion.
How do approvers find out something is waiting?
Pending posts are visible on the planner, and you can wire notifications through Nimply's automations — a Slack or Telegram message when a draft enters review, for example — so approvals don't depend on someone remembering to check.
Is this suitable for regulated industries?
It's built for exactly that pressure. When every post must survive compliance review — law, financial advice, healthcare — a status pipeline with role-gated sign-off means the review step is structurally impossible to skip, rather than a policy people are trusted to remember.
Make “nothing ships unreviewed” a property of the system
Set up roles, put every draft — human or AI — behind the same gate, and stop relying on everyone remembering to be careful.