Course Builder WP stores its courses, lessons, and quizzes as custom post types in wp_posts, with enrolment and progress data on wp_postmeta against the student's user ID. The default admin gives a course-by-course screen and a per-student profile, neither of which lets you scan all enrolments at once or filter by completion state across the catalogue.

SleekView reads the course CPT and enrolment postmeta directly, so a single view lists every enrolment with student email, course title, current lesson, and progress percentage as first-class columns. Saved views filter by completion state (completed, in_progress, not_started), enrolment date range, or instructor. Pivoting enrolments by student turns the long-format postmeta into a per-student progress grid: one row per learner, one column per enrolled course.

Inline edits route through any CRUD endpoints Course Builder WP exposes, so progress recalculations and completion hooks fire normally. Direct-table writes are available for the back-fill case where you don't want side effects, and conflict detection warns you if two admins edit the same enrolment at once.

Course Builder WP keeps its schema light by storing enrolment and progress data on wp_postmeta against the student user ID, which is good for portability and bad for visibility. The default WP admin treats postmeta as ad-hoc fields rather than first-class columns, so an enrolments-across-all-courses view doesn't exist out of the box. Course admins end up exporting CSVs to spreadsheets just to answer 'who's stalled this week,' which is fine once a month and terrible as a daily workflow.

Customer success agents need student histories visible during calls, not buried in a profile screen with twelve other widgets. L&D leads reporting program health want time-to-complete distributions and per-cohort completion rates, which means joining enrolment dates with completion meta. SleekView's job is to expose wp_postmeta as proper columns, save the joins as named views, and gate access by role.

The underlying data is unchanged; the workspace around it stops getting in the way.