Yes. SleekView reads the academy tables directly, so it works on the free Academy core install as well as the paid Academy Pro stack. Some vote sources, like the certificate request vote column and the live class question rating, only exist on Pro, but the board itself renders fine on either tier without extra config.

They do. The Academy mobile app increments the vote counter through the standard REST endpoint, which writes to the same column the desktop site uses. SleekView Feedback reads from that exact column, so a tap on the mobile app shows up on the board on the next render and counts toward the sort order.

Yes. The data source picker lets you filter the underlying query by course ID, lesson ID, taxonomy term, or any meta field stored on the question row. A single course, a final exam, or a curated set of high-signal lessons can each get a dedicated SleekView board on a separate WordPress page.

Status pill changes update the Academy question status column you mapped to the status field. That is the only write. The student question text, instructor reply, and review rating stay untouched, so instructors can revert a status by editing the column and any audit log plugin watching the Academy tables sees the change.

Hidden reviews and rejected questions drop off the board because SleekView queries only visible rows by default. If you want a moderator view that includes pending or hidden items, the query filter accepts a status array, so instructors can see them without exposing the rows to enrolled students reading 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 over fifty thousand Academy questions 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.

Yes. The board reads from the Academy tables independently of enrollment, so a public roadmap page can show course requests, votes, and statuses to prospective students browsing from search. Voting itself can be gated to enrolled students by checking the standard Academy enrollment meta on submit.

The board keeps rendering as long as the academy tables exist in the database. Deactivating the plugin freezes the data at the last write, so the board still serves with stale counts until reactivation. A migration to a different LMS drops the tables and SleekView falls back to a clear empty state instead of erroring on the page.