No. It is a complementary read view of the data SecuPress already records. The SecuPress dashboard remains the right place for configuration changes, scan triggers, and policy edits. SleekView focuses on the operational work of reviewing logs, which is where the default UI runs out of room.

No. Detection and blocking remain SecuPress's job. SleekView only reads from the SecuPress log tables, never writes to them, and never participates in the request lifecycle. Protection runs unchanged whether SleekView is installed or not.

You can annotate and acknowledge rows inline, which preserves SleekView's read-mostly stance and protects the integrity of the underlying SecuPress log. Block and unblock actions still go through SecuPress's own controls so the audit trail SecuPress maintains stays intact.

Yes. SleekView reads whatever SecuPress stores locally, free or pro. The Pro plugin writes additional event types (advanced anti-spam, malware-scan details), and those simply appear as additional rows or columns in your SleekView automatically without extra configuration.

Yes. Each site's tables are scoped per blog. On multisite you can build per-site security views, or build a network-level view that joins logs across blogs if your security posture treats the network as one operational unit with shared on-call.

Reads happen on demand using SecuPress's existing indexes on the log tables. There is no background polling, no scheduled job, and no extra index to maintain. Front-end traffic is completely unaffected because SleekView only runs when an admin opens a view in wp-admin.

SleekView focuses on the workspace itself; alerting can be layered through standard WordPress hooks, scheduled exports, or a complementary monitoring plugin. SecuPress also has its own notification system, which usually covers the alert use case while SleekView covers the review use case.

As long as SecuPress retains it. SleekView reads the live tables, so any pruning policy SecuPress applies (or that you apply through the database) is respected automatically. If your compliance regime requires longer retention than SecuPress's defaults, configure the plugin's retention or archive rows out before pruning.