Both. SleekView reads EDD CR tables and the _edd_cr_restricted_to 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 EDD Content Restriction update functions, which fire the same hooks the admin uses on a manual restriction change. Any custom listener you have on edd_cr_status_changed runs exactly as if you had edited the restriction from the standard post edit screen.

Yes. Card layouts are per board. Your protected posts board can show post, required download, author, and last access. A per download board can show download, post count, and revenue. Each board remembers its own card template so the team does not reconfigure when switching.

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

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

No. SleekView paginates cards per column instead of loading every protected post up front. The board fetches counts via an indexed meta query, and each column loads a window of cards on demand, so even a site with tens of thousands of protected posts stays responsive on hosting.

Yes. Any EDD CR related table with a status like column is a valid board. The per download summary, the access log, and the renewal queue all work the same way as the main protected posts board once you point SleekView at the right table and pick a column to group the cards on.

It stays in sync because there is no separate database. SleekView reads the same wp_posts table the WordPress and EDD CR admin read. Changes on the kanban appear in the post list immediately, and edits from the admin appear on the next board refresh without sync.