Uncanny Toolkit extends LearnDash with dozens of modules (Force Completion, FrontEnd Login, Group Code Registration, Course Resume), each adding behaviour layered on top of LearnDash's own tables. The data still lives in learndash_user_activity, learndash_user_activity_meta, and the learndash_pro_quiz_* family, with module configuration stored in wp_options rows keyed by Toolkit module name.

The default Uncanny admin shows enabled modules and their settings but doesn't surface what those modules actually did to learner records. SleekView reads the LearnDash tables and the Toolkit option keys together so admins see an audit row for every Force Completion event, a list of every Group Code Registration redemption, and a per-user Course Resume position visible alongside standard activity. Filter learndash_user_activity by activity_status and activity_meta tied to Toolkit-driven changes to separate manual edits from automated ones.

Inline updates to LearnDash records route through the standard LearnDash APIs (the same APIs Toolkit calls), so hooks fire normally. Toolkit module options surface as editable rows for admin convenience without changing how the modules themselves run. WordPress capability gating means support reps can see Toolkit-affected user state without being able to flip Toolkit settings.

Uncanny Toolkit's value is the operational reach it gives admins, force a completion, redeem a group code, redirect a login, resume a course, but operational reach also means accountability. The default Toolkit admin shows that a module is enabled and how it is configured, not who used it and on whom. Compliance reviews ask for a log of every admin-triggered completion in the last quarter, partner managers ask for a reconciliation of which codes redeemed into which cohorts, support reps ask why a particular learner is on lesson seven instead of lesson three.

All of those answers live in learndash_user_activity, learndash_user_activity_meta, usermeta, and wp_options, but only as raw rows. SleekView turns those rows into views that match how the team actually works. The auditor exports a quarter of completions with filters intact, the partner manager spots a code that over-redeemed, the support rep explains a learner's path in one screen.

Same data, finally legible.