Essential Addons ships ninety-plus widgets that drop into Elementor layouts. Each used widget is recorded inside the page's _elementor_data JSON and also written to the per-post _eael_widget_elements meta the plugin maintains to scope its CSS and JS bundles. The plugin's site-level toggle map lives in the eael_global_settings option.

The default Essential Addons settings screen is a flat toggle list. It cannot answer "which pages embed the Advanced Data Table widget", "which posts still use a widget we plan to disable" or "which authors are publishing pages with Essential Addons content". SleekView reads the same meta and option records and renders one paginated table with title, widget slug, author, status and last-edited columns.

Inline edits to status, slug or author route through standard WordPress update calls, so Essential Addons' bundle scoping refreshes exactly as it would after a save in the editor. The Elementor JSON itself is left alone. The editor stays the source of truth for layout. The table owns the inventory the toggle screen omits.

Essential Addons grows generously: ninety-plus widgets, a free tier and a long history of campaign-driven enablement. After two years on a busy install the question is no longer "is this widget enabled" but "is this widget used and by whom". That answer sits in _eael_widget_elements and _elementor_data on every page, but the default settings screen treats widgets as a flat toggle list.

SleekView reads the same meta directly and renders the audit as one table with widget slug, status, author and last-edited columns. Agencies get a deliverable. Performance leads get a clean-up brief.

Editorial ops get evidence that grounds training in real usage. The plugin keeps owning the editor and the toggles, the table owns the inventory.