It reads what you already capture. Block Bad Queries can be wired to log blocks to a custom table, an option store, or a piped log file. SleekView mounts a board on top of whichever store you use. You map the columns once and the board renders directly from the source, so there is no duplicate logging step to maintain alongside BBQ.

Yes. SleekView supports anonymous voting backed by cookies for client portal boards, and logged in voting for staff only views. Clients can watch a filtered feed of blocks on their own site without ever touching wp-admin, and you can flip the same view between public and private with one toggle on the block.

Pagination and filtering happen server side, so the board only loads the rows it needs to render the current page. SleekView uses any indexes you have on the timestamp, status, and vote columns, which means it stays responsive even when BBQ is logging tens of thousands of blocked requests during an active attack on a busy site.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can scope the board to a specific site, a specific pattern, or a specific severity. Different pages can show different boards, which is how most teams build per client status portals on top of the same BBQ block log table.

Status is a column on the block row, and most teams add a notes meta key next to it. SleekView reads both, so notes stay attached to the block across BBQ rule updates and plugin upgrades. The next admin opening the board sees the label and the latest note without leaving the page or opening a separate ticket tool.

They write back to the source column, which means any custom queries, scheduled digests, or compliance reports can sort blocks by score. Several teams use the score to gate which blocks go into a weekly client report, which makes the board operational instead of just a vanity dashboard sitting next to the BBQ admin screen.

Yes. SleekView exposes a JSON endpoint for the same data the on site board renders, so a separate status page or a custom client portal outside WordPress can read the BBQ events and the votes directly. The endpoint honours the same WHERE clause and status mapping, so the off site view never drifts away.

SleekView keys cards by the source row identifier. If a row is pruned the card stops appearing, but if you keep an archive of older block events the board can be pointed at that archive too. Most teams keep an archive of higher severity blocks for exactly this reason, so the team votes and notes survive the rotation.