User Switching writes basic switch and switch-back events to the WordPress action stream, but you usually want a dedicated audit logger to persist them as structured rows. SleekView reads whatever table that logger writes to, which gives the kanban a stable source of switch events to render.

Yes. You can revoke any active session by dragging its card from the active lane into the revoked lane. SleekView calls the User Switching revoke API, which ends the impersonation on the next page load and writes an audit row naming the security lead who triggered the revoke action.

Yes. Every drag writes a structured audit row naming the security lead who performed the drop, the source admin whose session was revoked, the target user account that was being impersonated, and the timestamp, which is everything a SOC or ISO audit reviewer needs to verify the policy.

Yes. SleekView views are configuration only, so you can build one board filtered to off-hours sessions and another to a specific admin role from the same audit table. Each lead picks a default board, and admins pin shared boards into the sidebar for the whole security team to use.

The audit data does not disappear, so the active lane still shows the historical session card with its original start time. The revoke action no longer fires because the plugin API is gone, so the card moves to expired automatically once the WordPress cookie times out and the audit logger records the end event.

Each card opens a side panel showing the originating IP, the user agent string, the source admin role, the target user role, and any custom audit fields the logger captures. Security leads review the full context of an impersonation without leaving the kanban to open the underlying audit log row.

Yes. SleekView respects WordPress capabilities, so you can require a senior security capability before a card lands in the revoked lane for an active session. Support managers can still acknowledge switched back sessions, but only the security lead can revoke a session that is still running.

SleekView reads and writes the existing audit logger tables without adding shadow tables for switch events. View configuration sits in its own small options row, so uninstalling SleekView leaves every audit event and revoke record exactly where the audit logger wrote it for compliance reviews.