The Tutor LMS Google Classroom integration mirrors paired classes locally as posts of post_type=tutor_gc_class with meta in wp_postmeta tracking the Google course id, owner, sync state, and last-sync timestamp. Per-student enrolment mirroring writes to wp_tutor_enrolled with the Google profile id stored as additional meta, and assignment sync state lives in wp_postmeta on the linked WP assignment posts.

The default integration screen shows a list of paired classes and a sync button per class. There's no built-in view that surfaces pairing health (which classes synced last and which are stale), no roster-mismatch queue (Google Classroom enrolment changed but the WP mirror is behind), and no assignment-grade audit (assignments pushed back to Google but the local grade doesn't match).

SleekView reads the paired-class posts, enrolment rows, and sync-state meta directly. A pairing-health view sorts paired classes by last-sync timestamp so admins spot stale mirrors. A roster-mismatch queue surfaces students enrolled in Google Classroom but not in the WP mirror (or vice versa). An assignment-grade audit compares local Tutor LMS grades with the last-pushed-to-Google value to catch bidirectional sync conflicts. Inline edits to re-trigger sync route through the integration's API so the sync runs with normal retry behaviour; direct table writes are available for forensic cleanup.

Integrations between WordPress LMS plugins and external platforms like Google Classroom are silent when they work and catastrophic when they don't, and the catastrophe usually shows up at end-of-term when grades don't match between systems and academic-appeal season starts. The Tutor LMS Google Classroom integration handles the mechanics of pairing classes, mirroring rosters, and pushing grades, but the default admin surface is configuration-oriented: pair a class, click sync, see a success message. What it doesn't provide is the operational workspace where admins live: which pairings are healthy, which are stale, which students show up in one system but not the other, which assignment grades drifted between local Tutor records and what was last pushed.

Those questions get answered today by spot-checking individual classes, which means they get answered too late. SleekView's job is to read the local mirror state the integration already writes, expose it as filterable views, and let admins, instructors, and compliance reviewers each build the saved view their role actually needs. Re-sync still runs through the integration's own API so behaviour stays consistent; SleekView just makes the operational picture visible.