Yes. You can map all three to one unified board, with the source type appearing as a category tag, or split them into three boards scoped by data source. Most LifterLMS sites start with one merged board because it keeps the top of mind issues visible regardless of which screen students used to submit them, then split later if traffic grows enough to justify it.

No. Vote counts live in a separate meta column SleekView creates on install. The original LifterLMS review rating, comment text, and quiz attempt rows stay untouched. Removing SleekView leaves all original data intact, and the LifterLMS Reporting tab continues to render the same numbers it rendered before, with no schema migration to undo on the way out.

Yes. The board reads through the same LifterLMS access plan filters that gate course content, so any user without the right access plan or membership sees an empty board or a paywall message you configure. Public boards for marketing also work, and you can run both in parallel with different shortcode parameters scoped to different membership levels.

SleekView adds an optional status meta key during install with a default of Open. Instructors update the status from the admin board UI, the WP-CLI command, or by writing to the meta directly during automation runs. Existing project management plugins like Gravity Flow or FluentBoards can also push status updates into the same meta key, keeping your workflow tools in sync.

No. SleekView listens to status pill changes and can optionally fire its own notifications, but it never touches the LifterLMS notifications table writes that drive enrollment and progress emails. You can disable SleekView notifications entirely and continue using LifterLMS notifications as your only outbound channel without losing any board functionality.

By default the board shows a vote count only, with optional avatars for the most recent voters. Anonymous voting hides all identifying details, while logged-in voting can surface a small avatar stack. Most LifterLMS sites pick logged-in with avatars for student dashboards and anonymous count-only for public marketing boards, controlled per board with a shortcode parameter.

The board paginates server-side with cursor-based queries on indexed columns, so large datasets stay fast. A library with fifty thousand reviews and a million quiz attempts renders the first page in under a second on standard managed WordPress hosting. Filters and category tags also use indexed columns, so combined filters do not degrade response times the way ad hoc admin search would.

Yes. SleekView reads through the language filters the multilingual plugin applies to queries, so cards appear in the visitor language when the underlying review or note was authored in that language. Sites can also run a board per language by passing the language code as a shortcode parameter, useful for cohort dashboards split across regions and timezones.