No. SleekView Feedback reads directly from whatever table BackWPup is using. You point it at the source, pick the columns for votes, status, category, author, and title, and the board renders. No ETL job, no sync, no duplicated data. Anything BackWPup writes shows up on the next page load of the board.

Yes. SleekView ships anonymous voting backed by cookies, so client stakeholders can upvote schedule changes and request new destinations without an account. You can also require login if you want the board scoped to staff, and the same view handles both modes with a single toggle.

Each visitor gets a cookie scoped vote token per item. Logged in users are tracked by user ID. SleekView also exposes a rate limit so one IP cannot spam the board, which keeps a public ops status page honest without forcing a signup wall in front of clients who only want to read the latest results.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can scope the board to nightly schedules, a single destination, runs from a particular site in multisite, or any combination of fields BackWPup stores. Different boards on different pages can use different filters.

A failure flag is just a category value on the row. You can write it into a meta key BackWPup already understands, or a dedicated column SleekView creates. Either way it shows up in the admin alongside the original run, so whoever owns BackWPup sees the flag without leaving the WordPress admin.

They write back to the source column, which means BackWPup reports and any of your own queries can sort future schedules and destinations by that score. Several teams use the score to gate which destinations get a paid storage tier, so the board is operational, not just a vanity dashboard.

Both. SleekView ships as a Gutenberg block, an Elementor widget, a Bricks element, and a classic shortcode. Theme developers can also call the render function from PHP and pass a configuration array, so the board can mount on any template, including a custom status page outside the main site.

The view paginates server side and only loads the rows it needs for the current page. Indexed columns stay fast even on long log tables. For large networks, scoping the board by subsite or schedule keeps both the query and the audience focused, so the page feels snappy at scale.