No. SleekView Feedback reads the llms_lesson post type and the watch log table that LifterLMS Advanced Videos already writes when a student plays a video. There is no separate roadmap table, no sync job, and nothing to migrate. Upvotes are stored as numeric meta on the same row your reports chart against, so totals stay aligned.

Yes. The Feedback view inherits the same query filters as SleekView Tables and Charts. You can restrict by lesson status, chapter, course, review state, or any custom meta. Most LifterLMS teams expose only lessons tagged Roadmap or Bug with statuses Planned, In progress, and Shipped on the public board and keep drafts hidden behind the admin.

SleekView tracks upvotes per browser through a signed cookie and per user ID for logged-in WordPress users. You can also require a LifterLMS enrolled account before voting if you want stricter dedupe. Vote totals stay consistent across page loads and devices for known users, with cookie-based dedupe protecting anonymous voters from double counting their own upvote.

A separate roadmap tool is a different product with its own database, login, and pricing. You sync lesson flags across, then maintain two sources of truth. SleekView Feedback reads LifterLMS data live through WordPress, so the board, the lesson editor, and the LifterLMS reporting tab always show the same numbers. There is one source of truth: your WordPress install.

Yes. Any numeric meta key can act as the vote column, any taxonomy or text meta can be the status, and any taxonomy or meta can be the chapter pill. The SleekView block exposes a dropdown for each role so you map the LifterLMS columns once through the block UI and never touch the underlying template to change which fields render.

By default upvotes update the meta silently to avoid spamming busy editors. You can opt in to firing a standard WordPress action on each upvote that you bridge into LifterLMS email triggers if you want producers to see live demand, or threshold it to alerts every ten or fifty votes for a calmer notification cadence inside your tools.

Yes. SleekView lets you scope the query to one or many terms in any taxonomy, so you can run a board per course, per unit, or per chapter. Each board is a separate block on a separate page, all reading from the same underlying lesson store with their own filter and column mapping configured for the cohort that sees it.

Because SleekView Feedback reads whatever query you point it at, you can swap the source from llms_lesson to a different post type or table without rebuilding the board. The cards, badges, votes, and filters stay intact. You re-map the column roles in the block settings, and the public URL stays the same for visitors and search engines alike.