It reads existing Sensei rows directly. The lesson comments, quiz answers, and progress events all live in wp_comments and wp_commentmeta, and SleekView queries those same tables with no schema changes. Vote counts get written to a new meta key on the same comment row, which is a non-destructive operation that any Sensei reporting plugin continues to ignore.

No. Sensei calculates completion and progress from the comment type and meta keys it already owns. SleekView never modifies those keys. The new vote meta key sits alongside the existing ones and is only read by SleekView itself, so progress queries, completion logic, and the learner dashboard keep returning exactly the same numbers and the same lesson states they did before the plugin was installed.

Yes. The shortcode accepts a course ID parameter and the board renders only the lesson comments, quiz answers, and progress events tied to that course. Sites typically embed a per-course board inside each course page, a per-module board on module overview pages, and a global board on the marketing roadmap, all reading from the same data with no duplication of any source row.

The board paginates server-side and uses the indexed columns Sensei already maintains on the comment table, so even very large catalogs render the first page in under a second on standard managed WordPress hosting. Filters by category, status, and course also use indexed paths. Combined filters do not degrade performance the way ad hoc admin search filters would on a busy Sensei site.

You choose the voting mode. Logged-in only uses the Sensei session and ties each vote to a user ID. Anonymous uses a per-device cookie and never requires registration. Most Sensei sites pick logged-in for paid courses to discourage gaming the vote totals, and anonymous on public marketing boards to lower the friction for prospective buyers who have not yet enrolled in any course.

Yes. The board reads through the same access filters Sensei applies to its own queries, so paid course feedback stays gated to the right learners. A public marketing board can run in parallel with a different shortcode parameter that restricts visible items to a curated list, so the sales page never accidentally exposes private course content from inside paid courses behind the paywall.

Yes. The board uses the standard WordPress comment threading model on the original comment row, so a reply from the instructor appears both on the board card and on the Sensei lesson page as a normal comment reply. Email notifications follow the standard WordPress comment notification path, so subscribers to the comment thread are notified about replies the same way they always have been.

The board keeps reading the rows that remain in the database. The cards continue to render with the data Sensei wrote, but new lesson comments and quiz answers will no longer be created because Sensei is no longer running. Re-enabling Sensei restores normal write behavior and the board picks up the new rows automatically, with no manual reconnection required during the upgrade.