The real-login cards work from WordPress's own user-meta last-login data, no extra plugin needed. The probe cards depend on having the access log readable or a login-attempt logger that records wp-login.php hits.

Yes. Each card supports a filter on the WordPress role. An administrator-only view shows admin login cadence separately from subscriber traffic.

Yes. The same data source feeds both, so a user reviewed in the table stays in sync with the donut on the next chart render. The charts are a second presentation over the same user table.

Probes are requests to wp-login.php after the rename has taken effect. The chart layer reads them from the access log or from a connected login-attempt plugin's log table, whichever is present.

Yes. Rename wp-login.php supports multisite, and SleekView Charts can scope cards per subsite using the site_id column on user meta and access logs.

Yes. Each WordPress role keeps its own saved dashboard layout. Security leads see the probe donut by default; site owners see the real-login KPI; firewall maintainers see the top-IP bar. Saved layouts ship per role without rebuilding the cards.

Charts query the live user meta and log tables on each render with paginated reads. The result is the same login state the access log would show, refreshed every time the dashboard loads.

Yes. Queries use the indexed timestamp columns on user meta and the connected log. Sites with high authentication volume render the dashboard in well under a second.