Moodle Bridge WP keeps a WordPress mirror of Moodle courses as the moodle_course CPT, with enrolment, role, and sync-timestamp data in wp_postmeta on the linked WP user. Sync configuration sits in wp_options under the bridge's option key. The default admin shows per-course sync status and totals, which is enough to confirm a sync ran but not enough to spot the one cohort whose enrolments lag behind Moodle.

SleekView reads the mirror CPT and bridge postmeta directly, so an audit view lists every WP user-course mapping with the last sync timestamp, current state, and Moodle role as first-class columns. Filters surface mappings where WP and Moodle disagree on enrolment, role, or completion. A separate view focuses on stalled syncs: rows where the bridge tried to push and the Moodle webservice returned an error, captured in postmeta or the bridge log option.

Inline edits route through the bridge's Moodle webservice client where supported, so changes propagate to the Moodle side and the standard sync hooks fire. Direct writes skip the bridge for back-fill scenarios after a data import. Multisite installations get per-subsite scoped views, so a campus-wide deployment can audit one school's mappings without leaking data across subsites.

Connecting WordPress to a Moodle instance is a reliable architecture for blended-learning organisations that want marketing and content delivery on WP and assessment on Moodle. The bridge plugin handles the sync, but operating a bridge in production means living with the reality that webservice calls fail, learner records lag, and SSO provisioning races against the next scheduled sync. The default per-course summary screens answer 'did anything sync' and obscure the row-level question every support team eventually has to answer: 'which specific user-course mappings are wrong right now and how do we fix them.' Bridge admins doing roster imports want a post-import audit that shows every mismatched row in one place, not a log file.

Support agents handling tickets want to see the affected mapping, its error history, and a re-sync button in one screen. L&D admins running compliance audits want exportable evidence that every WP enrolment has a corresponding Moodle enrolment. SleekView's job is to expose the bridge's WP-side state as a composable workspace.

Same data, finally addressable at the row level.