Both. SleekView reads Quiz Maker tables and the status column at the database level, so whichever tier you run the board still builds. Paid add-ons that add custom fields or extra status values are picked up automatically because SleekView scans the live schema on render.

SleekView calls the Quiz Maker reporting functions, which fire the same hooks the admin uses on a manual status change. Any custom listener you have on the Quiz Maker status changed event runs exactly as if you had edited the attempt result from the standard reports screen.

Yes. Card layouts are per board. Your attempts board can show student, quiz, score, and attempt time. A pass rate board can show quiz, attempts, and average score. Each board remembers its own card template so the team does not reconfigure when switching context at all.

Yes. SleekView respects every WordPress capability check Quiz Maker registers. A user who can view but not edit reports can drag a card to inspect, but the writeback only fires for users with the same capabilities the report edit screen would enforce on a manual save.

Add the new state in Quiz Maker the way you normally would, by adding a custom result value through the plugin filters or a custom report meta. SleekView picks it up on the next board load because columns are derived from the distinct status values present on rows, not hard coded.

No. SleekView paginates cards per column instead of loading every report up front. The board fetches counts via an indexed status query, and each column loads a window of cards on demand, so even a quiz site with hundreds of thousands of attempts stays responsive on standard hosting.

Yes. Any Quiz Maker related table with a status like column is a valid board. The per quiz pass rate, the question bank attempts, and the per cohort report all work the same way as the main attempts board once you point SleekView at the right table and pick a column to group on.

It stays in sync because there is no separate database. SleekView reads the same wp_ays_quiz_reports table the Quiz Maker admin reads. Changes on the kanban appear in the report list immediately, and edits from the admin appear on the next board refresh.