No. SleekView Feedback reads the llms_private_post post type and cohort meta that Private Areas Pro already writes when a thread is created. There is no separate roadmap table, no sync job, and nothing to migrate. Upvotes are stored as numeric meta on the same row your moderator 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 thread status, cohort id, category, review state, or any custom meta. Most teams expose only threads tagged Roadmap or Bug with statuses Planned, In progress, and Shipped on the cohort board and keep raw chat hidden behind the admin.

SleekView tracks upvotes per browser through a signed cookie and per user ID for logged-in WordPress users. Cohort areas require a LifterLMS membership account by default, so dedupe is enforced per member id without extra setup. Vote totals stay consistent across page loads and devices for cohort members on the private feedback board.

A separate roadmap tool is a different product with its own database, login, and pricing. You sync threads across, then maintain two sources of truth. SleekView Feedback reads LifterLMS data live through WordPress, so the board, the thread list, and the moderator admin 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 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 moderators. You can opt in to firing a standard WordPress action on each upvote that you bridge into LifterLMS email triggers if you want moderators to see live demand, or threshold it to alerts every ten or fifty votes for a calmer notification cadence inside your existing tools.

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

Because SleekView Feedback reads whatever query you point it at, you can swap the source from llms_private_post 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 members and search engines alike.