phpList is an open-source self-hosted email application, and the WordPress plugin is a thin signup bridge. The base URL, REST credentials and default list IDs live in wp_options; per-form list routing is stored as block attributes or shortcode arguments embedded in post_content; when the optional submission log is enabled, each handoff lands as a row keyed to form ID, list IDs and a submitted_at timestamp.

SleekView reads that WP-side data and renders one row per signup embed: parent post, form_id, list_id, embed_type (shortcode or block), confirmation flag and last edited timestamp. When the submission log is on, every submission row also surfaces with submitted_at, list IDs and source page. Filter to one list_id to see every embed feeding that newsletter. Sort by submitted_at on the log view to follow today's capture cadence. Filter to confirmation_flag=off to catch single-opt-in surfaces before the next compliance review.

The plugin keeps owning the credentials, the runtime REST handoff and the embed shortcode. The table view owns the audit surface, so the signup inventory the plugin already writes stops hiding inside per-post editors and becomes one queryable grid for editorial, marketing and compliance.

phpList is the long-standing open-source choice for organisations that want their list off a SaaS, and the WordPress plugin is the visitor-facing front door for most of those installs. The trade-off is that the WP side of phpList has been a configuration screen, not a reporting one, and the per-embed answers live inside per-post editors and a submission log nobody opens. A signup form that went missing during a redesign, a list quietly absorbing every signup while a niche newsletter goes silent, a confirmation flag flipped on staging and not on production: each of those is a real row in the plugin's own data, and a table is the surface that makes them visible at once.

SleekView reads the same wp_options, post_content, postmeta and submission log the plugin already writes, then renders the result as a sortable admin grid. The plugin keeps owning the runtime REST handoff; the table view owns the inventory the editorial team and the DPO both needed.