User Switching exposes switch_to_user, switch_back_user, and switch_off_user hooks for every impersonation event. It does not log them to a persistent table by default, so the audit trail comes from pairing User Switching with an event logger such as Simple History or with a small custom plugin that writes events to a dedicated table.

Once that audit table is in place, SleekView Charts reads it directly. Switching admin, target user, event type, source IP, and timestamp become dimensions on Number, Pie, Bar, and Area cards. The dashboard summarises a week or a month of impersonation activity in a screen, instead of leaving the question to be answered by ad-hoc SQL or scrolling.

Charts are read-only by design. Audit data is something to read, not edit, so the dashboard is a compliance surface that pairs with the SleekView table view for incident response and CSV export. The User Switching runtime is untouched.

An audit table is only useful if someone reads it. Logs that nobody opens are checkbox compliance, not real compliance. SleekView Charts turns the captured switch events into a dashboard that compliance leads can open weekly and incident responders can scope in seconds.

The numbers are honest because the cards read directly from the audit table without writes, and the data stays inside WordPress under capability gating. The result is a working compliance surface that respects the audit trail rather than competing with it.