No. SleekView Feedback reads directly from the activity log table on your MainWP dashboard install. You point it at the source, pick the columns for votes, status, category, and event metadata, and the board renders. No ETL job, no sync, no duplicated rows. Anything the activity log captures shows up on the next page load.

Yes. SleekView ships with anonymous voting backed by cookies, so clients on a portal page can upvote events without ever seeing the MainWP admin. You can also require login if you want the board restricted to staff, and the same view handles both modes with a single toggle in the block settings.

Each visitor gets a cookie scoped vote token per item, and logged in users are tracked by user ID. The plugin also exposes a rate limit so a single IP cannot spam the board, which is enough to keep public client portals honest without forcing a signup wall in front of every reader.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can scope the board to events from a specific site ID, a specific severity, or a specific event type. Different pages can show different boards, which is how most agencies build per client status portals.

Status is just a column on the row. You can write notes into a meta key Activity Log for MainWP already exposes or a dedicated column. Either way the value shows up next to the event in the MainWP admin, so the next tech who picks it up can read what was decided without opening a separate ticket system.

They write back to the source column, which means any of your own queries, custom dashboards, or scheduled digests can sort events by score. Several agencies use the score to gate which events go into a weekly client report, which makes the board operational instead of 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 you can mount the board on any template, including a custom MainWP dashboard tab.

The view paginates server side and only loads the rows it needs to render the current page. You can index the vote, status, and timestamp columns, and SleekView will use them. Several MainWP agencies run the board on dashboards with tens of millions of events without measurable load.