Yes. SleekView Feedback works with the free WP Symposium Pro plugin because it reads the standard symposium_activity table and group taxonomy. Paid add-ons add additional meta fields that can be used as sort sources or pill values, but the base board functions fully on a vanilla Symposium install without any paid add-on dependency.

Yes. SleekView queries activity posts through the standard Symposium group permission layer, which honors private group visibility. A logged-out visitor never sees private group activity on a public board, and a member sees only the groups their Symposium membership grants access to read, with the rest hidden cleanly from view.

Yes. The query builder accepts a group ID filter, so you can build a board scoped to a single Symposium group, a board scoped to two related groups, or a global board that pulls from every group on the site. Filters compose, which means a Bug-reports-only Pro-members-only board is a few configuration clicks away.

Yes. The Upvote button inserts a real like via the Symposium like API, which is the same write path the native activity stream like button uses. Symposium notifications fire to the original poster, reputation tallies update, and badge add-ons listening for like events see the new engagement exactly as if it came from the activity stream itself.

SleekView reads the live group ID stored on the activity row, so a moved post immediately picks up the new group's category pill on the next render. Likes stay attached to the activity post regardless of which group it ended up in, so the vote count is preserved across any reorganization of the Symposium group structure.

Yes. The chat module writes to its own tables and does not interfere with symposium_activity, which is the only table SleekView Feedback reads. Chat messages are not shown on the board because they are not activity posts, which keeps the board focused on long-form community suggestions instead of conversational chat noise from elsewhere in the plugin.

Yes. Any custom meta written to an activity row by a third-party plugin or a snippet is visible to SleekView in the data source picker. A Phase or Severity meta added by your team becomes a status source on the board the moment it is saved, with no extra configuration required inside the SleekView admin settings.

Trashed and hidden activity posts disappear from the board on the next render because SleekView only queries published activity by default. If you want admins to see hidden items in a moderator-only board, the data source supports a status array so trashed activity can be included when the board is scoped to admin-only visibility.