Yes. SleekView reads the BuddyBoss tables directly, so it works the same way whether you run the free BuddyBoss Platform plugin or the paid Pro stack with the App add-on. Vote counts, favorites, and topic tags come from the same database rows regardless of which license tier you have installed.

They do. The BuddyBoss App favorites the topic through the REST API, which writes to bp_user_favorites the same way the web favorite button does. SleekView Feedback reads that table, so a tap in the mobile app shows up on the board immediately and counts toward the sort order on the next render.

Yes. The data source picker lets you filter the underlying query by group ID, forum ID, taxonomy term, or any meta field stored on the topic. A LearnDash course group, a private members-only forum, or a single public discussion category can each get its own dedicated board on a separate WordPress page.

Status pill changes update the BuddyBoss topic tag you mapped to the status column. That is the only write. The original forum topic, activity post, and favorite counts stay untouched, so moderators can revert a status by editing the tag, and any audit log plugin watching the topic taxonomy sees the change.

Trashed and hidden topics drop off the board automatically because SleekView queries only published topics by default. If you want a moderator view that includes hidden items, the query filter accepts a status array, so admins can see Pending or Spam rows without exposing them to members.

No. SleekView paginates the underlying query, caches the sorted set, and only fetches the rows it needs to render the current page. A board with fifty thousand BuddyBoss topics serves in the same time as a board with five hundred because the database does the heavy lifting once and the cache covers every subsequent visitor.

Anonymous voting is off by default because it does not write back to bp_user_favorites, which expects a user ID. You can enable a SleekView session-based fallback that stores guest votes in its own table and merges them on login, useful for public roadmap pages that get traffic from non-members.

The board keeps rendering as long as the underlying tables exist. BuddyBoss and BuddyPress share the same bp_ schema for forums, activity, and favorites, so a migration in either direction does not break the SleekView config. If the tables disappear entirely the board fails closed with a clear empty state instead of a fatal error.