No. SleekView reads the wp_comments table, joined commentmeta values, and the depth metadata WP Thread Comment writes onto each comment. The only write is the upvote increment, which lands on a commentmeta key you choose so it sits next to the rest of the comment data row in WordPress.

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 at all on the WordPress site.

You map a wtc_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 wp_comments has stored. Threads attached to posts, pages, custom post types, and product reviews 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 comments 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 upvote meta is preserved on the trashed row for export and history.

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

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