Admin Menu Editor (by Janis Elsts) serializes the entire customized admin menu into one big array, stored in wp_options under ws_menu_editor. Each entry carries title, file (the menu slug), capability, icon, position, and any per-role visibility overrides. The plugin's drag-and-drop editor is excellent for editing the tree, but it is not a queryable view. Auditing what Subscribers actually see still means opening the editor, role-switching, and reading the tree one node at a time.

SleekView reads ws_menu_editor directly, unpacks the tree, and renders one row per menu node. Title, file, parent, capability, icon, position, and per-role visibility (Administrator, Editor, Author, Contributor, Subscriber, custom roles) become first-class sortable columns. Saved views can scope the grid to one role's blocked items, every top-level item, or every menu node renamed away from the WordPress default.

Inline edits route through the plugin's own update path, so the cached menu the plugin builds for each request is invalidated correctly and capability changes take effect on the next admin page load. Bulk hide for a role, bulk rename a section, or export the entire customized tree as CSV for a change-control record.

Admin Menu Editor solved a real problem the moment it shipped: the WordPress admin menu is rigid and uncustomized menus leak features to roles that should never see them. The plugin gives you a powerful drag-and-drop editor for building the tree you actually want, role by role. What it does not give you is an audit surface for that tree once it has more than a handful of overrides.

Editing is one job and reviewing is a different job. Auditing what Subscribers can reach in a fifty-node customized tree, across half a dozen roles, with capability overrides on every other branch, is not what drag-and-drop is designed for. A flat grid with one row per node, sortable columns for capability and position, and filterable columns for each role, collapses an hour of clicking into a single saved view.

The plugin still owns the schema, the cache, and the editor. The grid just lives next to the editor as the audit lens that the editor does not pretend to be.