It works with both, and reads from the tables either component writes to. MemberPress Courses lessons and quiz attempts merge into the same board as base MemberPress member meta, so the visible cards reflect feedback across the entire member experience, not just the course component. You can also scope a board to course feedback only with a shortcode parameter if needed.

Yes. The shortcode accepts a membership level parameter, and the board reads through MemberPress access filters to gate cards to the right tier. Sites typically embed a tier-specific board inside each membership level dashboard, plus a global board scoped to admins. All three boards read from the same underlying rows with no duplication, only different visible filters at the query layer.

No. MemberPress calculates quiz scores from the answer meta inside wp_mepr_quiz_attempts, which SleekView never modifies. Vote counts live in a separate meta column SleekView creates on install. Quiz scores, the gradebook, and any third party reporting plugin built on top all continue to read exactly the same data they read before SleekView was installed on the site.

SleekView adds an optional status meta key on install with a default of Open. Course owners update status from the admin board UI, the WP-CLI command, or by writing to the meta directly during automation runs. Sites that already use a project management plugin can map the status column at the existing field, so the workflow tool stays in sync with the public board state shown to members.

Yes, when the board is configured to accept submissions. SleekView ships with an optional submission form that supports text, image upload, and a link field, all stored as meta on the new row. The image upload uses the standard WordPress media library, so existing upload limits and quota settings stay in effect without requiring any separate media storage path.

Yes. SleekView paginates server-side using indexed columns on the WordPress comment table, the MemberPress quiz attempts table, and the meta key SleekView writes for votes. A membership site with twenty thousand members and a million attempts renders the first page in under a second on standard managed WordPress hosting. Combined filters use indexed paths, so response times stay fast.

Yes. The board reads through MemberPress trial filters, so trial members can be shown a restricted board with fewer cards or a different status filter. Most sites configure trial members to see the same board paying members see, on the theory that visible roadmap activity is one of the highest leverage trial-to-paid conversion levers available to a course-driven membership site.

Cards submitted by the canceled member stay on the board with the original vote counts. SleekView never deletes rows based on membership status, because that would break the historical record other members upvoted. The canceled member loses the ability to vote and submit, but their existing contributions remain visible. Reactivating the membership restores their voting and submission ability automatically.