WP Admin UI Customize lets a site admin hide menus, change the login screen, restyle the dashboard, and rewrite admin colours per role. Every one of those settings lives as a serialized array inside wp_options, under keys that follow the wpadminui_* pattern (for example wpadminui_settings for global config and wpadminui_role_ for per-role overrides). The default screens spread those rules across half a dozen tabs, so auditing what a Subscriber actually sees means opening every tab in turn.

SleekView reads those option keys, unpacks the serialized arrays, and renders one row per rule. Role, target (admin bar, menu, dashboard widget, login screen, color scheme), action (hide, rename, restyle), and the rule's current value become first-class columns. Filters scope the grid to one role, one target, or one action at a time, so you can answer questions like "what has Editor been blocked from?" in a single view.

Inline edits go through the plugin's own update_option flow, so saving a change re-runs whatever validation and cache-clearing logic the plugin attaches. Bulk toggle, copy a rule from one role to another, or export the rule set as CSV for an internal audit. The plugin still owns the storage. SleekView just makes it legible.

Locking down the WordPress admin per role sounds simple until you actually do it. Subscribers should not see Tools. Editors should not see Plugins.

Contributors should see a renamed login screen and a custom dashboard widget. WP Admin UI Customize gives you the controls, but the UI it ships is organised the way the plugin thinks (by feature area), not the way an admin audits (by role). The result is half a dozen tabs to reconstruct what a single role actually sees, every time you onboard a new user.

A grid that flattens every rule into one row per (role, target, action) collapses that audit into a single saved view. Filters answer the questions that matter at access-review time: what is Editor blocked from, where did the Login screen branding drift to, which roles still have the welcome panel visible. Copying a rule set from Editor to a new role becomes a bulk action instead of a re-entry exercise.

None of this changes how WP Admin UI Customize stores its settings. The rules still live in wp_options. The grid just makes them legible at the scale a real WordPress site actually uses them.