tutor_quiz_attempts and tutor_quiz_attempt_answers for grading, tutor_earnings and tutor_withdraws for monetisation, the course post type for catalogue and joins to wp_users for student or instructor email. SleekView only reads what Tutor Pro has already written.

When SleekView routes the edit through the Tutor Quiz API, the standard completion and notification hooks fire. Direct DB writes skip hooks by design for back-fill scenarios where you do not want side effects.

Yes. Filter tutor_withdraws to status pending, select rows and bulk-flip status to approved. SleekView writes through the Tutor APIs where supported so instructor notifications still send.

Yes. Tutor Pro stores marketplace commissions in the same tutor_earnings table, with instructor_amount and admin_amount as columns. SleekView shows both alongside the parent order ID.

Yes. Add a filter for user_id and every column narrows to that instructor. Useful for instructor self-service so each one sees their own grading queue, earnings and payouts.

Tutor Pro writes assignments and certificates as custom post types and meta. SleekView reads them through the same post-type and postmeta surface that powers the rest of the workspace.

Yes. Any filtered set exports as CSV with the same columns the view shows. Finance uses it for reconciliation and head instructors use it for course retros.

No, it is an additional admin surface. Tutor Pro's own screens stay where they are. SleekView gives instructors, ops and finance the row-level workspace they need without disturbing the plugin's workflow.