No. SleekView reads the AcademyPress enrollment and progress records in place and renders columns from the live data. There is no separate sync step and no second database to keep in line with the source, so what you see on the board matches the plugin admin at all times.

Yes. SleekView writes status changes through the AcademyPress API rather than editing rows directly, so any hook the plugin fires for enrollment changes, certificate issuance, or onboarding email sequences still runs exactly as it would after a manual change in the admin.

Yes. Each board has a filter layer that runs before the columns are built, so you can scope it to a single course, a specific cohort, a payment status, or a date range. Course leads usually keep one focused board per launch while a wider board watches lapsed members.

You pick any field on the enrollment record, the linked course, or the user profile. Common combinations are member name, course title, percent complete, last activity date, current lesson, and tier badge. Date and currency fields render in your site locale so cards stay easy to scan.

It runs alongside the standard admin. The kanban is an alternative view of the same enrollment records, so anything you change on the board appears in the plugin admin and anything you change in the plugin admin appears on the board on the next load.

Yes. SleekView respects WordPress capabilities, so you can grant your support team a role that lets them view and drag cards on a board scoped to their courses while keeping them out of broader site administration. Read-only boards are also supported for stakeholders.

Columns load with pagination per column rather than fetching every record at once, and filters are pushed to the database so the page stays fast even with tens of thousands of rows. You can also archive completed cohorts so old boards do not slow down the current ones.

It complements them. Static reports and exports still answer batch questions about totals and revenue, while the kanban gives you a live work surface where staff actually move members through the lifecycle without leaving the page or queuing another export.