Both. SleekView reads Edwiser Bridge 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 Edwiser Bridge sync API, which fires the same hooks the admin uses on a manual sync action. Any custom listener you have on edwiser_enrollment_status_changed runs exactly as if you had retried the enrollment from the standard Edwiser Bridge admin screen.

Yes. Card layouts are per board. Your enrollments board can show student, Moodle course, sync time, and attempt count. A response log board can show error code, attempt, and last sync. Each board remembers its own card template so the team does not reconfigure when switching.

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

Add the new state in Edwiser Bridge the way you normally would, by adding a custom sync state through the plugin filters or a custom enrollment meta. SleekView picks it up on the next board load because columns are derived from the distinct values on rows, not a hard coded list.

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

Yes. Any Edwiser Bridge related table with a status like column is a valid board. The Moodle response log, the per course summary, and the dedupe table all work the same way as the main enrollments board does once you point SleekView at the right table to group cards on a chosen column.

It stays in sync because there is no separate database. SleekView reads the same wp_eb_enrollment table the Edwiser Bridge admin reads. Changes on the kanban appear in the enrollment list immediately, and edits from the admin appear on the next board refresh.