Birim Approvals – Post Approval Workflow For Clients & Editors Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
WordPress lets a contributor submit a post for review, but it does not say who must approve it, it does not remember what they approved, and anyone who can publish can skip the step. Clients and legal reviewers usually approve by email, and someone publishes by hand. Birim Approvals replaces that with a real sign-off.
A publish gate
- Choose which content types need approval: posts, pages, any custom post type, and media files.
- Until the required people approve, a post cannot be published or scheduled: not from the block editor, the classic editor, Quick Edit, the REST API or another plugin.
- Administrators can publish anyway only by giving a reason, which is recorded.
Approval of the exact version
- An approval counts only for the version it was given on (title, text, excerpt and featured image; for files, the file itself and its title).
- If anything changes afterwards, earlier decisions stop counting, approvers are told, and publishing locks again. Nobody can sneak in an edit after the client said yes.
Approvers inside and outside WordPress
- Team members decide in the editor or under Dashboard > Approvals, with a preview, even if their role cannot edit posts.
- Clients, legal, compliance do not need an account. Type their email as an approver and they get a personal, expiring link to a review page with Approve and Request changes.
- A shared link for teams: let anyone at
@client.comapprove after confirming their email with a one-time code. A forwarded link alone can never approve. - Works with Public Post Preview: if you already share drafts with it, those preview pages show the same approval box.
- Choose whether every approver must approve or any one is enough. Requesting changes always needs a comment and always blocks.
Files too
- Ask a client to approve a logo, a contract or a set of photos from the media library. They download it through their link. Replace or rename the file and they are asked again.
- Works with Birim Private Files: approvers can open protected files they are asked to approve.
Notes
- On WordPress 6.9 and later, optionally require all editor Notes to be resolved before publishing.
A record you can rely on
- An audit log of every request, view, approval, change request, reset, link and override: who, when, on which version, with comments, IP address and browser. Download it as CSV.
- IP addresses and browser details are removed after a period you choose; the decisions are kept.
- Works with WordPress’s privacy tools (export and erase personal data).
- A dashboard widget shows what is waiting for you and what you are waiting on, and
[birim_approvals]lists open requests for reviewers on a front-end page.
Lightweight
No build tools, no tracking, no external requests. Emails are sent by your site.
Screenshots
Publishing is refused until the right people approve. The Approvals box shows each approver, including a client outside WordPress, and a requested change with its comment.
What a client sees: a review page with Approve and Request changes. No account needed.
A team member’s inbox under Dashboard > Approvals, with a preview link.
All approvals are in for this exact version: ready to publish.
Settings: which content needs approval, link expiry, data retention and the audit log.

