tutor_quiz_attempts and tutor_quiz_attempt_answers for grading, tutor_earnings and tutor_withdraws for monetisation, the course post type for enrolment, and joins to users for instructor email. SleekView only reads what Tutor has already written.

No. The chart view runs aggregations against the tables directly. Inline edits in the table view route through the Tutor Quiz API where supported so completion hooks fire, but chart rendering is read-only and never triggers downstream effects.

Yes. Group a Pie or Bar by user_id on tutor_earnings with Sum on instructor_amount. The donut variant labels each slice with the instructor name. Useful for marketplace review and for quarterly retention conversations with top earners.

Filter tutor_quiz_attempts to attempt_status equals review_required and render an Area card grouped by attempt_ended_at. The line goes up when grading slows, down when an instructor clears the queue. A reliable early warning before the student emails arrive.

Yes. tutor_withdraws stores a status column. Render a Pie grouped by status to see pending versus approved versus rejected, with the date filter scoped to the payout window finance cares about.

Yes. The aggregations use standard table indexes on user_id, course_id and the timestamp columns. Date-scoped charts stay fast at scale. All-time aggregates without a date filter are heavier and opt-in per view.

Yes. Add a filter for user_id and every card narrows. Useful for instructor self-service dashboards (their earnings, their pending withdrawals, their grading backlog) without exposing other instructors' data.

Yes. Any chart card can drop down to the table view of the same dataset, and exports respect the column choice. Finance gets a CSV that matches what they see on the dashboard, not a separate report.