WP Coursify Pro registers course as a custom post type with related unit and lesson records, and tracks per-student progress in wp_postmeta keys plus its own enrollment table. The default admin is a series of profile-shaped screens: one for each course, one for each student, one for each unit. Anything you want to see as a list (every student progressing in course X, every unit unfinished across the catalogue) needs custom queries.

SleekView reads wp_posts filtered by the Coursify post types and joins them with the enrollment and progress rows so course managers can compose the catalogue and student views they actually need. A course-completion table sorts learners by progress per course. A unit audit lists every unit with completion rate across all enrollees. A stalled-learner report filters where progress is stuck below a threshold and last activity is older than a chosen date.

Inline edits to enrollment status route through Coursify's own functions where they exist so any course-completion hooks fire normally. Direct-table edits skip hooks by design for back-fill scenarios. Multisite installations get per-subsite scoped views automatically.

Course programs run on cohorts, and cohorts run on progress: who's where, who's stuck, who needs grading, who's about to drop off. Coursify gives you everything you need to run those courses, but its admin is built around the unit of work (a course, a student, a unit) rather than the unit of operations (a cohort moving through a course). When an instructor needs to see who's stalled in week three, the answer is in the database but not on any screen.

When a program lead wants completion rates across the catalogue, the data is there but the aggregation is custom-built every time. When customer success needs to answer 'which unit did I get stuck on' for a learner on the phone, the profile screen tells a story one click at a time. SleekView's job is to expose the underlying tables as a composable workspace so each role can build the view their job actually requires.

The data is already in WordPress; it just needs a row-shaped surface that matches how learning operations actually run.