Admin Menu Editor stores its entire configuration inside a single serialized option named ws_menu_editor. The structure encodes every top-level item, every submenu, every renamed label, and the per-role visibility flags. The plugin's UI lets administrators edit that tree. What it does not do is summarize it.

SleekView Charts treats the parsed option as a data source. Each role and each menu item becomes a row in a virtual table with columns for role, item_id, visible, custom_label, and original_label. From there, dashboard cards write themselves. A Number KPI counts overrides applied. A Bar chart ranks roles by visible-item count, surfacing which role has the most cluttered admin and which has been carefully trimmed. A Pie chart splits hidden items vs custom labels vs untouched defaults.

For agencies running multi-client installs, the dashboard becomes the single screen that says whether menu hardening was actually done. Custom-label coverage as a percentage. Hidden items per role. Overrides by section (Posts, Pages, Plugins, Users). Roles that should have a stripped admin but still show every default item stand out as bars that should be much shorter. The plugin still owns the editor; SleekView Charts owns the audit picture.

Trimming the WordPress admin is one of those tasks that lives entirely in habit. An admin opens Admin Menu Editor, drags items, toggles role flags, saves. Days later nobody remembers exactly what changed, and weeks later a new client install is supposed to look like the last one but the team is operating from memory.

The configuration is fully recorded in the ws_menu_editor option, just not summarized anywhere a human reads. SleekView Charts parses the option, expands it to one row per item per role, and renders the picture. Number of overrides applied, hidden items per role, overrides by section, visible items per role.

Agencies use it as proof of work. Compliance reviewers use it as an audit artefact. Multi-site operators use it to spot installs where the standard hardening was forgotten.

The plugin was always recording the truth; the dashboard is finally the layer that reads it.