Workflow
How Editant works
Editant adds a sidebar to the WordPress block editor and a dashboard to the admin. Together they handle the full review cycle: generate a link, send it to a person, gather their comments and decision, and keep the record.
From draft to sign-off in five steps
Step 1
Open any post and generate a review link
A new Editant sidebar appears in the block editor for posts, pages, and any public custom post type. Click Generate review link. The plugin creates a random token, hashes it for storage, and gives you a single URL to share. Optional settings cover the link’s expiry (default 30 days) and whether reviewers must identify themselves before commenting.
Step 2
Send the link to your reviewer
Copy the URL and send it however the project works: email, chat, a calendar invite, a project tracker. The reviewer opens the link and sees the rendered post as it will publish. No login required.
Step 3
Reviewers comment and decide
On the preview page, reviewers see the content alongside a threaded comment panel and an Approve / Request Changes decision panel. If you’ve required identity, they enter their name (and optionally an email) once. They reply to each other and to the author. The author gets emailed when comments arrive.
Step 4
You see everything in one place
The Editant dashboard in the admin lists every active and recent review link across your site, with status, last activity, and approval count. The block editor sidebar shows the threaded comments and decisions for the post you’re working on. Reply, regenerate the link, revoke access, or open a new link from the same place.
Step 5
The record stays with the post
Every comment, reply and decision is stored on your site against the post it refers to, with the reviewer’s captured identity and a timestamp. A Request changes decision sends the draft back to you; when you have made the edits, a re-review request emails the reviewers and the cycle runs again on the new version. Nothing leaves your database. Requesting a re-review
With Pro
Free Core records who said what and who approved. Pro turns that record into evidence and gives the people in the loop better tools.
- Comments in the text. Reviewers comment on a sentence or a block, and the passage is highlighted for them and for you in the editor. Reviewing in the text
- Suggestions as tracked changes. Reviewers propose the exact wording; you accept or reject each one. Suggesting changes
- Quorum before publish. Two of three reviewers, or all of them, before the Publish button unlocks. Publish quorum
- A signed approval. Each decision is signed against a hash of the content as it stood, and every event goes into an append-only log where each entry is chained to the one before. Export approvals as PDF certificates or JSON, verifiable with the site’s public key. Signed approvals and the audit log
- What changed since the last approval, shown to the reviewer so a re-review reads only the difference. Comparing changes
Behind the scenes
- Tokens are SHA-256 hashed before they hit the database. Even a backup leak would not expose them.
- All public endpoints are rate-limited (default 30 requests per IP per minute, configurable).
- Reviewer identity is captured per link and scoped per post. The same person reviewing two different posts gets two distinct sessions.
- WordPress’s GDPR data export and erasure hooks are wired in. Right-to-be-forgotten requests work out of the box.
- Translation-ready, multisite-aware, and compatible with any block editor theme.
Continue: Who it’s for → Read the documentation