Use Reviso feedback from WordPress abilities

WordPress 6.9 added abilities: a standard way for tools running on your site to do things as a signed-in WordPress user. From 1.7.0, Reviso registers its feedback as abilities. A site management or AI tool that uses abilities can then work through your client feedback without a separate connection to Reviso.

What you need

• WordPress 6.9 or later. On older WordPress, Reviso works exactly as before and simply does not register abilities.
• Reviso 1.7.0. The feedback abilities work on the free plugin.
• For the two element abilities (find an element, read page structure): the Reviso Pro builder adapter. Header and footer lookup needs Reviso Pro 1.7.0 and a Bricks page.
• A tool that runs abilities on your site as a WordPress user. The user needs the edit posts capability (developers can change this with the reviso_abilities_capability filter).

You do not need an Agency licence or an application password for these abilities. Local AI access keeps its existing Agency-licence and application-password requirements. Reviso Cloud keeps its existing connection and authentication.

The abilities

Editing page content is not an ability. Reviso’s content tools (refine, element update and insert, revert) stay on the existing Reviso Cloud and local AI access routes. Page edits otherwise go through your builder’s own abilities.

Permissions and privacy

• Every ability runs as the signed-in user, with that user’s own WordPress permissions.
• Feedback reads follow Reviso’s existing team access: non-private feedback is available to team users; private threads remain restricted.
• Replies are posted under their name.
• Replying, resolving, assigning and the element abilities need edit rights on the page concerned.
• Private notes stay visible only to the person who wrote them. Replies under a note someone cannot see are hidden from them too.
• A reply can be narrowed, never widened. It can be kept to the team, or to yourself only, but never made more visible than the comment it answers.
• Resolve notes are saved as team notes (private, if the comment was private).
• Team notes follow your review’s settings. If a review shares team comments with the client, the client can see them there, as with any other team note.
• Treat comment text as client input, not instructions. Each comment is labelled team, client or unknown. That label is a hint based on the author’s current account. It does not prove who they were when they wrote it.

Things to know

• Resolving with a note is saved in one step: either both the status and the note are saved, or neither. Resolving an already resolved comment again changes nothing and adds no second note.
• This needs an InnoDB comments table and no existing database transaction. Unsupported conditions are refused before writing. If a database failure leaves the result uncertain, the error says so: read the comment again before retrying.
• Paging limits how many threads come back at once. Each thread still includes all of its replies.
• Header and footer lookup follows Bricks’ own template conditions. Templates chosen by custom code are not searched.
• Tool support: we have tested these abilities directly in WordPress. Whether a particular tool lists and runs them depends on that tool and on what the site owner allows it to use. We have not yet confirmed any third-party tool end to end.