No. SleekView reads existing symposium_activity, symposium_likes, and symposium_friends rows. Any upvote increment writes back to the Symposium likes row for the activity post, so the count stays in sync with the member wall. Status pill edits land on a postmeta key you choose, separate from Symposium 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 members 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 sym_review_status postmeta key on the activity post when you build the view. SleekView shows a colored pill for each value, and any post 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 symposium_activity has stored. Posts, photo posts, replies, and group activity 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 today.

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

When the underlying activity post is deleted, SleekView removes the card on the next refresh. If the post is hidden rather than fully deleted, the card disappears from the public view but the Symposium likes rows are preserved on the hidden post for export and history purposes later.

Yes. SleekView views render as shortcodes, Gutenberg blocks, and short HTML snippets. Most teams drop a Top likes view above the Symposium member wall on a Community page so members see the upvote board and the chronological wall share the page without any visual conflict.

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