Yes. SleekView Feedback queries wp_ld_zapier_triggers, wp_ld_zapier_logs and the related meta tables that LearnDash Zapier already writes. There is no sync step, no export, and no separate datastore. Every card on the board reflects the current row in WordPress at the moment the page is loaded.

Upvotes write back into the same row the card was rendered from. SleekView uses the vote count column and the trigger_status value that LearnDash Zapier maintains, so existing dashboards, reports, and email digests continue to work without any modification.

SleekView respects WordPress capabilities and exposes per role controls for voting, commenting, and status changes. A typical setup lets logged in members vote and submit, while LearnDash admins who run Zapier automations on staff roles move cards through planned, in progress, and shipped lanes.

SleekView paginates and lazy loads cards so a board with thousands of rows still renders in well under a second. Filters and sort controls run as indexed SQL queries against the LearnDash Zapier tables, which means scaling the board is a database problem, not a JavaScript one.

Yes. The shortcode renders for anonymous visitors with vote and submit buttons disabled unless the visitor logs in. Many LearnDash Zapier teams use this exact pattern for a public roadmap that anyone can read while only members can upvote and add new items.

SleekView reads custom taxonomies, post meta, and plain columns the same way. Map any of them to the category tag slot in the view config and pick a color per value. The board reuses the labels LearnDash Zapier already writes, so reports stay consistent across surfaces.

No. SleekView does not modify or replace the Default LearnDash Zapier list. The feedback board is a new view on top of the same data, which means staff can still use the familiar admin screen while members and customers interact with the public board side by side.

Yes. Each status change can fire an email to the original submitter, an admin notice, or a webhook out to other tools. The trigger fires the moment the LearnDash Zapier row updates, so members hear about planned and shipped moves without anyone composing a manual update.