SleekView reads whichever eg_ tables Essential Grid creates on your install. The base grid table and skin table exist in all reasonably recent versions, and source-specific features (Posts, Custom items, Social streams, WooCommerce) write to additional fields that SleekView surfaces as columns when those features are active. SleekView itself does not gate any column behind an upgrade.

For custom-item grids, basic item fields like title, alt text, and media reference are editable inline through the standard custom-item update path. Layout-affecting changes like skin reassignment or source-type changes are also supported where safe. Complex layout work still belongs in the grid editor, which SleekView complements rather than replaces.

Yes. Grids that pull from WooCommerce products show the WooCommerce source type and resolve the current product count at query time. Useful for spotting product grids that are unexpectedly empty because their category filter no longer matches any products, or for auditing which product categories each grid surfaces.

Social-stream grids show their configured platform (Instagram, Twitter or X, YouTube, etc.) and account as columns. The actual stream items are fetched at render time from the social platform, so SleekView surfaces the configuration and last-fetch metadata rather than every item. Useful for auditing which social grids are still pointed at active accounts vs ones that may have been deleted or rate-limited.

Yes. Select multiple grids and apply a skin change as a bulk action. SleekView writes through Essential Grid's grid update path, so caches refresh and the front-end picks up the new skin on next page load. Useful when migrating off a legacy skin or standardising on one design across the site.

No. SleekView paginates against the existing eg_grids indexes and only loads the rows on the visible page. The eg_ tables are already indexed for the Essential Grid admin, so the same indexes serve SleekView's grid. Saved views do not pre-fetch anything until they are opened, and the front-end grid rendering is completely unaffected.

Yes. SleekView is admin-only, it does not change how Essential Grid grids render on the front end. Shortcodes, the grid block, and template-tag inserts all keep working exactly as they did. The management layer is what changes, the rendering layer is untouched.

Yes. Each subsite has its own eg_ tables (with the appropriate prefix), and SleekView respects that scoping. Views show only the grids for the current site, which matches how Essential Grid itself behaves on multisite. Network admins can switch between sites and each one renders its own grid catalogue independently.