Both. SleekView reads WP Fusion Pro tables and the sync_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 WP Fusion Pro queue API the same way the admin does. The plugin fires its normal wpf_user_updated and tag application hooks, so any downstream listeners, like a webhook into your CRM or a custom logger, still run exactly as if the row had been edited from the queue screen.

Yes. Card layouts are per board. Your sync queue board can show user email, CRM id, tag set, and last attempt time. A retry board can show error code, attempt count, and the next retry time. Each board remembers its own card template so you do not have to reconfigure when switching.

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

Add the new value the way WP Fusion Pro normally would, either through a plugin setting or by adding a custom status hook. SleekView picks it up on the next board load because columns are derived from the distinct values present in sync_status at render time, not from a hard coded list.

No. SleekView paginates the queue per column instead of fetching every row at once. Each column loads a window of cards and pulls counts via an indexed query, so a six figure queue with tens of thousands of failed rows still renders fast on standard hosting.

Yes. Any WP Fusion Pro table or related meta with a status like column is a valid board. The tag log can be visualized too, grouped by tag, and the contact creation queue works the same way as the main sync queue because they share the schema shape.

It stays in sync because there is no separate database. SleekView reads the same wp_wpf_contacts rows the WP Fusion Pro admin reads. Changes made on the kanban board appear in the queue list immediately and changes from the admin appear on the next board refresh.