Yes. SleekView reads from any Academy Pro table that ships with a vote counter and a status column, including academy_certificate_requests, academy_live_questions, and the standard academy_reviews table. As new Pro add-ons land, the data source picker shows the new tables and you wire them up the same way.

They do. The Academy Pro mobile app increments the vote counter through the same REST endpoint the desktop site uses. SleekView Feedback reads from that exact counter column, so a tap in the app shows up on the board on the next render and counts toward the sort order without any mobile-specific config.

Yes. The data source picker lets you filter the underlying query by course ID, certificate template ID, live class ID, or any meta field stored on the row. A single course, a single certificate type, or a curated set of high-signal live classes can each get a dedicated SleekView board on its own WordPress page.

Status pill changes update the Academy Pro status column you mapped to the status field, whether that is request_status on the certificate table or question_status on the live class table. That is the only write. The original request, vote total, and instructor reply stay untouched so a status revert is just another column edit.

Rejected and hidden rows drop off the board because SleekView queries only visible rows by default. If you want a moderator view that includes rejected or pending rows, the query filter accepts a status array so instructors can see them without exposing the rows to enrolled students browsing from the public course page.

No. SleekView paginates the underlying query, caches the sorted set per page slug, and only fetches the rows it needs for the current page. A board with over fifty thousand certificate requests 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 the Academy Pro vote counter expects a user ID. You can enable a SleekView session-based fallback that stores guest votes in its own table and merges them on enrollment, which suits public catalog pages where marketing wants prospective students to influence the upcoming course slate.

The board keeps rendering as long as the underlying academy tables exist. Pro-only columns like certificate request status disappear on downgrade, so SleekView falls back to the standard academy_questions and academy_reviews tables and the board reflects only the rows that still have valid data on the free tier.