Publication Approval Workflows: Governance Without the Friction
Paminga's new Approval Workflow gives your team a structured review process for marketing assets before they go live — authors request review, designated approvers review and comment, and only approved content gets published.
If your team has ever shipped a typo to a 200,000-contact send, you know exactly why this exists.
The goal: keep your brand consistent, reduce errors, and give the right people visibility into what's going out the door — without slowing anyone down with unnecessary process.
How the Review Process Works
Every asset starts as a Draft. From there, it moves through a clear set of states:
- Draft — being worked on. Only the author interacts with it.
- Review Requested — submitted for review. Approvers are notified.
- Changes Requested — an approver asked for revisions. The author is notified.
- Approved — signed off. Ready to publish.
- Published — live.
Authors can withdraw a review request at any time. Approvers can approve directly from Review Requested or Changes Requested status — no extra clicks.
Two-Tier Approvers
Approvers are the users who can approve, request changes, or publish assets that have been submitted for review. Paminga supports two tiers:
- Instance-Wide Approvers can review and approve assets across your entire Paminga instance — regardless of which Workspace an asset belongs to.
- Workspace-Specific Approvers are additive — they can approve assets within a specific Workspace in addition to the instance-wide approvers.
Big team with regional sub-brands? Drop a Workspace-specific approver into each Workspace. Smaller team? Stick with instance-wide and you're done.
Threaded Comments, Combined with Status Changes
Comments are a running conversation attached to an asset's review. Authors and approvers can leave comments at any point during the process.
Threaded replies stay organized. An unread comment indicator lets you know when someone has added to the conversation.
Approvers can combine a comment with a status change in a single action — leave the feedback and request changes in one move. No copy/paste between Slack and the builder.
Notifications, Three Ways
When a review is requested, a status changes, or a comment is added, Paminga notifies the relevant people through up to three channels:
- Notification Center — the bell icon in-app
- Banner — a prominent in-app banner for approvals
- Email — a summary email with a direct link to the asset
Each user configures their own preferences under Personal Settings → Notifications. All channels are on by default.
The Approval Queue
The Approval Queue is your central hub for managing the review process — every asset that's waiting for review, has been reviewed, or is approved and ready to publish. A badge on the menu item tells you how many items need your attention.
Three filtered views handle the common workflows:
- All — assets you submitted, assets assigned to you, assets in Workspaces where you're an approver
- Submitted by Me — track where your content stands
- Approved, Pending Publication — the "ready to go live" list, for teams that batch their publishing
Publish Without Approval
Most teams want process for most users, but need certain roles to bypass it — your CEO posting a hot-take CTA on launch morning, for instance.
The Publish Without Approval permission grants exactly that. Users with this permission see a Publish button alongside the Request Review option, letting them skip the review process when appropriate. Configure it in Permissions under the Assets category.
Get Started
- Go to Account Settings → Approvals and toggle approvals on
- Designate one or more Instance-Wide Approvers — and Workspace-Specific Approvers if you need them
- Submit your next asset for review and run a dry pass with your team
Read the Approvals docs and the Approval Queue docs for the full walkthrough.
