No. SleekView is read-only against the WSAL schema by default. It queries wp_wsal_occurrences and joins wp_wsal_metadata for display, but the plugin continues to write events through its own pipeline. Annotations and tags applied through SleekView are stored separately so the WSAL audit chain stays intact.

Yes. Any key written to wp_wsal_metadata — whether by WSAL itself, an add-on, or a custom alert you register — can be promoted to a column. Once it is a column it behaves like any other field: sort, filter, group, or include it in saved views and CSV exports.

WP Activity Log Premium can write to a separate database. SleekView reads through the same connection definition, so if WSAL is configured to log to an external table, point SleekView at that connection and the grid stays consistent with the source of truth.

Yes. Filtered rows export with the exact columns visible on screen, including any custom metadata fields you have promoted. Exports respect the active filter, the sort order, and the pagination range, so the file matches what the reviewer signed off on.

SleekView paginates server-side and uses the indexes WSAL already maintains on occurrence ID, alert code, and user ID. Logs with millions of rows stay responsive because the grid never tries to load the whole dataset; it requests one page at a time with the active filter.

Yes. SleekView respects the capability checks WSAL defines, so only users with permission to view the activity log see the grid. You can layer additional capability checks per saved view to limit who can open compliance-sensitive filters.

SleekView does not replace WSAL's alert engine, but saved views work as a stable target for scheduled reports. Pair a view like Failed logins last 24h with a CSV export on a cron and route it to your security inbox or SIEM, while WSAL keeps real-time alerting where it belongs.

The Reports add-on is good for scheduled summaries with predefined templates. SleekView covers the day-to-day investigation step before reports — exploring the data, discovering the right filter, then locking it into a view. The two complement each other: explore in SleekView, then promote to a scheduled WSAL report when the pattern is stable.