Yes — those are post types (course, lesson, llms_quiz), and SleekView treats them like any other CPT. Course progress and quiz attempts come from the custom tables, but the post-type joins let you show course title and quiz title alongside attempt data without manual lookups. Drag-and-drop columns from either source live alongside each other in one view.

lifterlms_quiz_attempts.questions stores per-question answers in a serialised column. SleekView can show that as a related child view per attempt, decoded into rows with question text, student answer, correct answer, and points awarded. Useful for grading manually-reviewed quizzes and for spotting questions where students consistently get the same wrong answer.

Where SleekView uses the LLMS_Quiz_Attempt API (status changes, grade overrides), the standard hooks fire — auto-grade, completion notifications, certificate issuance, group progress updates. Direct DB edits skip hooks by design for back-fill scenarios where you don't want side effects. Pick per view based on whether the operations should trigger downstream effects.

Yes. Memberships (llms_membership) and access plans (llms_access_plan) are post types with metadata, so SleekView shows them as standard CPT views. Voucher tables (lifterlms_vouchers, lifterlms_voucher_code_redemptions) are exposed if you need redemption audit views — useful for tracking promo-code usage or partner-program redemptions.

Yes — save views per role and filter to the courses or quizzes that instructor authored. The author-id filter on course or llms_quiz posts gives you per-instructor scoping naturally. Combined with WordPress capability gating, each instructor sees only their cohort's grading queue and progress data.

Yes — each subsite has its own LifterLMS tables, and SleekView reads the current site's tables only. Useful when an organisation runs separate LMS instances per department or per region. Cross-site aggregations aren't supported (each subsite is independent), but per-site dashboards behave as expected with role-scoped views per subsite.

Achievements and certificates are stored as posts (llms_achievement, llms_certificate) earned by users, with relationships in lifterlms_user_postmeta. SleekView exposes per-user achievement and certificate lists as either pivoted columns on a student view or as separate audit views — useful for spotting students close to a milestone for marketing follow-up.

Yes. Any SleekView view exports to CSV or JSON. Useful for a weekly grading log delivered to stakeholders, or for archiving graded attempts to an external learner-record store. The export respects the column choice in the view, so the result matches what you saw on screen — no surprise extra columns or missing fields.