SleekView reads stored test result rows, so it works best with the Health Check & Troubleshooting plugin because that plugin persists results between runs. The core Site Health screen recomputes most tests on demand, which leaves less stored data for the kanban to render.

Yes. The Health Check plugin keeps a rolling window of test results, and SleekView reads whatever sits inside that window. A common pattern is to keep the latest run of each test plus a short history, which is plenty for a triage board to render lanes.

No. Acknowledge is a triage flag SleekView writes to a small extension column. The default Site Health screen still shows the test exactly as Health Check ran it, and the WordPress core screen still surfaces the underlying status. Acknowledgement only changes what the SleekView board displays.

Yes. SleekView views are configuration only, so you can build one board filtered to security tests and another to performance tests from the same Health Check dataset. Each maintainer picks a default board, and admins pin shared boards into the sidebar.

SleekView reads the test category list on every page load, so a new category shows up automatically as a value inside the filter bar. No kanban reconfiguration is required, and you can immediately filter the active lanes to that new category to triage tests in it.

Each test card opens a side panel showing the full description, the recommendation text, the actions Health Check suggests, and the category and severity. Maintainers can triage, acknowledge, or snooze directly inside the kanban without opening the original Site Health screen tab.

Yes. SleekView respects WordPress capabilities, so you can require a security lead capability before a card lands in the acknowledged lane for the critical severity in the security category. Junior maintainers acknowledge recommended tests, but only seniors close criticals.

SleekView reads and writes the existing Health Check test result rows without adding shadow tables for Site Health data. The triage status sits in a small extension column the kanban manages, and uninstalling SleekView leaves every test result exactly where Health Check wrote it.