Skilljar is a hosted training platform that integrates with WordPress (vendor or third-party) for SSO-based course access and embedded enrollment flows. The integration caches Skilljar enrollment state, SSO identity mappings, and gated-page assignments locally so the WP side can gate content without per-request API calls. That cache lives in wp_options for plugin state, wp_usermeta for the WP-user-to-Skilljar-learner identity mapping, and wp_postmeta for gated-page assignments.

SleekView reads all three layers and presents them as one table. Support looks up a WP user to find their Skilljar learner ID and current enrollment list, sync engineers see drift between local cache and the expected refresh window, and L&D admins audit which WordPress pages and product groups map to which Skilljar courses or paths.

The Skilljar dashboard remains the source of truth for enrollment progress, certifications, and revenue. SleekView's role is to make the WordPress-side cache addressable for the reconciliation and SSO-mapping audits that the hosted UI can't perform because the mapping data only exists locally on WordPress. Inline edits affect local cache only and are limited to reconciliation fields like manual drift overrides.

Skilljar is built for enterprise training programs where customers, partners, and employees need course access governed by SSO and tracked by department, role, or contract. The WordPress integration is a small but important piece of that picture, it lets the WP marketing or portal site enroll learners and gate pages by Skilljar entitlements without exposing the LMS internals. The fragility is in the SSO mapping and the enrollment cache, which both live on WordPress and drift quietly when an SSO provider changes a claim, a Skilljar course gets renamed, or a gated page loses its backing path.

The Skilljar dashboard can't help diagnose any of that because the mapping is local, and the default WordPress admin can't help either because the cache lives in options and usermeta without column access. Enterprise rollouts amplify the cost of every unresolved access ticket because each one threatens contractual SLAs. SleekView's job is to make the local mapping and cache addressable as a table with SSO audit columns, drift flags, and a reconciliation queue, so the access tickets that do land get resolved in minutes from one screen.

Same data, no SQL, dramatically less risk in an enterprise tier where uptime of the learner experience matters.