The student-courses enrolment table, the lesson completion records and the assignment grade tables. Specific table names depend on the Namaste version, and SleekView's column picker rescans on startup to keep up with schema changes.

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

Yes. Group a Pie or Bar by course_id on the enrolment table. The donut variant labels each slice with the course title from the related Namaste course post.

Filter the assignment table to rows with no grade yet and render an Area card grouped by submission_date. The line goes up when instructors fall behind and down when the queue clears. A reliable early warning.

Yes. Group by completion_date on the lesson completion table with weekly or monthly grouping and a Bar or Area card. Useful for seasonality reviews and for spotting an engagement dip after a curriculum change.

Yes. The aggregations use standard table indexes on course_id, student_id and the date 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 course_id and every card narrows. Useful for course owners self-servicing their own dashboard without depending on programme-wide admin access.

Yes. Any chart card drops to the table view and exports respect the column choice. Useful for sharing a CSV of the catalogue retro with an external advisor or for archiving before a curriculum overhaul.