ClientEdits administrator reference

Private attachments

New reviewer files are stored in a dedicated per-site directory outside web-accessible storage. Downloads require an authorized owner or the correct active reviewer invitation. An administrator can set CLIENTEDITS_PRIVATE_DIR to an absolute path outside every public web root when the host cannot provide a writable default. The upload fails if the store cannot be verified. On upgrade, administrators can resolve previously uploaded files from the migration notice. Choose private migration for review-only files, or keep deliberately public assets as ordinary WordPress media. Previously shared URLs or cached copies can require separate cleanup at the original host or CDN.

= Does a suggestion change the live page? =

No. The reviewer sees a receipt that the suggestion was received. The page changes only after an editor approves that version and ClientEdits verifies the saved result. Approving an unpublished post or page keeps its publication status.

= Who can use a review link? =

Anyone who has the link, until it expires, is revoked, or the review is closed. A display name is a label, not a verified identity.

= What content can be updated directly? =

Direct edits cover verified text in paragraphs, headings, flat list items, buttons, supported Classic HTML, titles, excerpts and selected block attributes. The editor preserves supported inline formatting and checks for conflicts. Builder support depends on the stored structure and the verified adapter. A passage marked comment-only can still receive feedback. See “Builder verification” for the direct-write policy.

= Can I undo? =

For ordinary post body edits the saved page must still match the verified update. External fields and shared targets use their adapter’s saved-state and permission checks. After a later edit, ClientEdits shows the before and after wording and does not restore the page.

= Does ClientEdits send email? =

The site sends a verification email when a reviewer enters an address. The address is saved on the review link before confirmation; reply alerts start only after that reviewer confirms it on a confirmation page. Unsubscribe links likewise require confirmation, so an email preview opening a link cannot change the setting. At review creation, the owner can choose email alerts for new feedback. These alerts go to that review creator's WordPress account address, at most once per review per hour and eight times per address per day. A separate optional daily count of waiting suggestions goes to the site's WordPress administration email. Verification requests are limited per review link and recipient. Email notices do not include the suggested wording. Mail uses the site's existing WordPress mail, so delivery depends on that site's mail setup.

= What happens if a page changes during review? =

ClientEdits compares the saved passage and page history before a direct update. If it cannot establish that the proposal still applies, it stops and asks the editor to compare the current wording. Core editor saves loaded before a ClientEdits update receive a stale-save warning.

= What personal data is stored? =

Review links may contain a reviewer label and an optional email address with its verification state. The address is stored when verification is requested, including before confirmation. Suggestions, page completion, replies, notification records, and undo/audit snapshots stay in your WordPress database. WordPress's email-based privacy tools find linked review data when that address is stored on the review link; notification rows are also matched by recipient address. They cannot locate an anonymous reviewer by email. Browser drafts stay on that device; expired drafts are cleared when a ClientEdits review next opens. ClientEdits suggests text in WordPress's privacy-policy editor for site owners to adapt. An owner can export the whole review, then close it so eligible records enter retention; pending suggestions and uncertain saves are kept for review. Erasure can retain approved page wording, records with audit operations, and owner-authored replies. Review those separately if they contain personal data.

= Can clients review an unpublished page? =

Yes. The owner must select the saved post or page for the review. Eligible drafts open in the active theme. ClientEdits checks the invitation, its review cookie and a short-lived signature for that one draft on every preview request. Reloading the review obtains a fresh preview address while the invitation is active. Revoking the link, reaching its expiry or closing the review stops new access.

The preview uses the saved draft and same-origin theme assets. Scripts, external embeds and assets hosted on other domains are blocked in the private frame. ClientEdits verifies that the template actually displayed wording from the selected draft through WordPress's content filter. Readable text is available if the theme fails or a custom template skips that filter, such as a layout built entirely from custom fields. Password-protected pages, private posts, pending items and scheduled items use the readable view. Approval updates the saved wording. Publishing stays manual unless the owner authorizes it when creating the review.

The review and draft preview send private, no-store and noindex headers. If a hosting cache or CDN overrides WordPress response headers, configure it to bypass requests containing clientedits_review, clientedits_open or clientedits_draft_preview and requests with ClientEdits review cookies.

= How does publishing on sign-off work? =

When creating a review, select “Publish drafts when reviewers sign off” and set the required number of reviewer sign-offs. Send a separate invitation to each reviewer. WordPress must still authorize the review creator to edit and publish each draft when the quorum is reached. Expired or revoked invitations cannot contribute a vote. The review lists the outcome for each eligible draft. An authorized owner can cancel outstanding publication from the review.

The comparison covers the stored post, its saved custom fields (including builder and SEO data) and its assigned terms. It ignores routine editor locks and Elementor's generated preview caches. Elementor's saved document, page settings and authored styles are checked. Changes to a shared template, a linked media file or another external resource are outside that comparison. If a draft changes after the review starts, including through an approved suggestion, it needs a fresh review or a manual publishing decision.

After publication, open the review and choose “Move back to draft” to withdraw an eligible version. If the published version has since changed, use the normal WordPress editor to decide what to do. Returning a page to draft cannot recall copies already cached or distributed.

= Builder verification =

ClientEdits supports direct edits to plain text in these tested native controls:

* Elementor Free 4.4.1 — the title of a classic Heading widget.
* Beaver Builder Lite 2.11.2.2 — the text of a Heading module. A separate unpublished builder draft can require you to finish or discard it first.
* Breakdance 3.0.2 — the plain text field of a Heading element.
* Oxygen 6.2.2 — the plain text field of a Text element.

In Oxygen 6.2.2 and Breakdance 3.0.2, clicking Save or using the native save shortcut waits for the last pending change in the supported text control. If a save is already running, a second save request from that tab waits for the first one to finish. Text typed during a save stays marked as unsaved until you save it. Reload open builder tabs after upgrading.

The owner needs permission to edit both the page and its builder content. If a ClientEdits decision happens while a supported visual editor is open, keep a copy of unsaved wording and reload before saving. A fresh editor loads the approved wording.

Other versions and field shapes default to comment-only feedback. This includes the Divi, Bricks, WPBakery, Avada, Thrive Architect and Oxygen Classic integrations. A site integrator can opt in a locally tested adapter using the clientedits_verified_builder_adapter filter. Its arguments are the default boolean, adapter ID and WP_Post. Verify the native editor, rendered page, unrelated fields and Undo on the exact site configuration before opting in.

= How are WooCommerce variations and Advanced Custom Fields handled? =

For eligible WooCommerce variations using the standard product store, ClientEdits reads and writes the plain customer-facing description. WooCommerce manages the generated variation name and attribute summary. Rich descriptions accept comments. Older proposals targeting a generated variation name or summary require a fresh review of the description.

If a variation description changes while its native WooCommerce editor is open, the older tab can save its other changes, such as a new price. WooCommerce displays a notice to reopen the variation before changing its description.

For supported ACF text fields, approval and Undo run ACF field validation before writing. A character limit or a custom field validation rule can reject the wording.

= What happens if my webhook or Slack endpoint is down? =

ClientEdits records one delivery per configured destination when you release a publishing hold. The review and delivery tables use InnoDB transactions to commit the publishing decision and its notifications together. When notifications are enabled, a database that cannot commit both leaves the hold in place. WordPress Cron sends each destination independently. An unavailable receiver can recover while the review owner continues working. A successful response must have an HTTP status from 200 to 299.

A connection failure, HTTP 408, 425, 429 or a 5xx response triggers retries after 1 minute, 5 minutes, 15 minutes, 1 hour, 4 hours, 12 hours and 24 hours. A longer Retry-After value extends the wait. When HTTP 429 or 503 includes a valid Retry-After, other queued deliveries to that URL also wait, up to seven days. A separately configured URL can continue receiving events. A delay longer than seven days, another HTTP failure, or eight unsuccessful attempts leaves a failed delivery for an administrator to inspect. Delivery uses WordPress safe HTTP checks for the configured HTTPS destination. Private addresses and nonstandard ports can be rejected under the site’s HTTP policy. Redirects are disabled. In ClientEdits > Settings > Webhook deliveries, filter by Failed and choose Retry delivery after fixing the receiver. This starts another retry cycle for that destination. Terminal records stay in the history for 30 days.

The generic JSON payload and event time stay the same across retries. If a signing secret is configured, verify X-ClientEdits-Signature against the request body using HMAC-SHA256 and the current secret. Use X-ClientEdits-Delivery to record each delivery once. Each destination gets its own ID, including when both settings point at the same URL. If your receiver processes an event and its acknowledgement is lost, ClientEdits may send the same event again. Slack incoming webhooks can display a duplicate in this case. Changing or removing a destination cancels outstanding deliveries for its previous URL.

Retries run when WordPress Cron runs. Low-traffic sites that need predictable timing can invoke WordPress Cron from their host scheduler. After a longer gap, due work resumes on the next run.
