No. SleekView reads the existing Thrive vote, badge, and comment tables. Any upvote increment writes back to the Thrive vote row for the parent comment, so the count stays in sync with the inline UI. Status pill edits land on a commentmeta key you choose, separate from Thrive vote data entirely.

Yes. The Upvote button supports guest votes with a per-IP and per-session lock to keep counts honest. If you would rather restrict votes to logged-in users or specific roles like Editor or Moderator, you can flip that in the view settings without touching any code on the WordPress site at all.

You map a tc_review_status commentmeta key on the parent comment when you build the view. SleekView shows a colored pill for each value, and any thread without a status simply renders without a pill rather than blocking the card from showing on the board at all in public.

Yes. SleekView reads whatever Thrive has stored. Threads attached to posts, pages, custom post types, and product pages all surface as cards on the board, grouped by the category chip you pick during view setup without any special configuration step at all on a multisite install.

Yes. Every saved view has its own role and capability scope, so you can publish a public Reader Feedback wall on an editorial page and a separate Moderator Triage queue that only Moderators and Admins can see. Both views share the same Thrive data underneath.

When the underlying parent comment is deleted, SleekView removes the card on the next refresh. If the comment is moved to trash rather than fully deleted, the card disappears from the public view but the Thrive vote rows are preserved on the trashed comment for export and history.

Yes. SleekView views render as shortcodes, Gutenberg blocks, and short HTML snippets. Most teams drop a Top votes view above the Thrive comment block on a flagship article so readers see the upvote board and the inline Thrive thread share the page without conflict.

SleekView paginates and sorts at the database level rather than loading every Thrive vote row into memory, so a site with hundreds of thousands of comments still renders the top of the feedback board in well under a second on a normal shared host with default caching enabled today.