No. SleekView Feedback reads the Sensei course and lesson post types plus the course_progress table that Sensei Pro already writes. There is no separate roadmap table, no sync job, and nothing to migrate. Upvotes are stored as numeric meta on the same row your Sensei Analysis reports chart against, so totals stay aligned across surfaces.

Yes. The Feedback view inherits the same query filters as SleekView Tables and Charts. You can restrict by course status, Sensei module, instructor, review state, or any custom meta. Most Sensei teams expose only courses tagged Roadmap or Bug with statuses Planned, In progress, and Shipped on the public board and keep drafts 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 Sensei 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.

A separate roadmap tool is a different product with its own database, login, and pricing. You sync Sensei courses across, then maintain two sources of truth. SleekView Feedback reads Sensei data live through WordPress, so the board, the course list, and the Sensei Analysis 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 category. The SleekView block exposes a dropdown for each role so you map the Sensei 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 instructors. You can opt in to firing a standard WordPress action on each upvote that you bridge into Sensei email triggers if you want instructors to see live demand, or threshold it to alerts every ten or fifty votes for a calmer notification cadence.

Yes. SleekView lets you scope the query to one or many terms in any taxonomy, so you can run a board per Sensei module, per instructor, or per language. Each board is a separate block on a separate page, all reading from the same underlying course store with their own filter and column mapping configured.

Because SleekView Feedback reads whatever query you point it at, you can swap the source from Sensei course 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 URL stays the same for visitors and search engines alike.