WP Activity Log Pro extends the same schema the free plugin uses: wp_wsal_occurrences holds the event with severity, alert code, user, and IP, while wp_wsal_metadata stores the variable context as key/value pairs. The premium tier adds wp_wsal_sessions for active logins, scheduled reports, and external storage destinations. The built-in viewer is excellent for browsing but funnels you through fixed filter widgets.

SleekView reads all three tables as one source. Each occurrence row promotes its metadata keys into named columns, so post titles, plugin slugs, role names, and custom alert keys become first-class fields you can filter and sort on. Active sessions from wp_wsal_sessions appear as their own grid, with the IP, browser, and last activity time on every row.

Saved views become the unit of work for compliance teams: pin failed logins in the last 24 hours, plugin changes this week, role escalations across all sites. Switch between them with a click, share them with auditors, and export the exact columns evidence requires for SOC 2 or ISO 27001 without rebuilding the search every time.

Premium audit data is only as useful as the questions it can answer. WP Activity Log Pro captures the right events with the right context, but a fixed-column viewer makes every question feel like a fresh search. Compliance frameworks expect repeatable answers, evidence with the same columns each quarter, and the ability to share a slice with an auditor without rebuilding it.

The metadata pivot in wp_wsal_metadata is where the interesting fields live, and a default UI cannot promote them to first-class columns without code. Add wp_wsal_sessions and you finally have the missing context: who was logged in when the event fired. Treating WSAL Pro as a real grid changes the tempo of investigations and the cost of every compliance review.

Pin the views your team revisits, hand them to auditors, and stop rebuilding searches when the question comes back. The premium tier already paid for the data; the grid is what makes it work.