White Label CMS stores its configuration inside wp_options under keys like wlcms-options and wlcms_branding. Each key holds a serialized array of settings: agency name, login logo URL, dashboard widget content, and per-role hide rules across the menu, admin bar, and footer. The plugin's settings screen spreads those across half a dozen tabs (Branding, Login, Dashboard, Menus, Settings), so auditing what Subscribers actually see takes a click trail.

SleekView reads the option keys directly, unpacks the serialized arrays, and renders one row per setting. Target (login logo, dashboard widget, menu hide, admin bar, footer credit), role (or All), current value, and the last-updated timestamp become first-class columns. Saved views can scope the grid to one client's brand setup, one role's hide rules, or every change made in the last week.

Inline edits route through update_option the same way the plugin's own forms do, so caching, validation, and any do_action hooks the plugin attaches still fire. Bulk-copy a brand kit from a template site to a new client, or roll back last week's branding change without scrolling through the change log.

Agencies live on White Label CMS. The plugin is excellent at restyling the admin so a client never sees a WordPress logo, a version footer, or a developer-y settings tab they should not be touching. What the plugin does not give you is a way to audit the white-label state across twenty clients at once.

Every site has its own brand kit, its own login screen, its own dashboard widget content, and its own per-role hides, all spread across five settings tabs. When a client complains that the wrong logo is showing on login, the admin opens five tabs in sequence to find the rule. A grid built on the underlying wlcms_* options collapses that into one filter.

Branding versus role hides versus footer credits all live in one queryable surface. Bulk-copying a brand kit to a new client becomes an action instead of a re-entry exercise. Rolling back last week's logo change becomes a one-line filter on Updated date.

None of this changes how White Label CMS stores its data. The plugin still owns the schema. The grid just gives the people who actually operate the white label a workspace that matches how they think about the work.