Yes. Envira Lite and Envira Pro both store galleries as the envira CPT with image data in postmeta. SleekView reads that the same way regardless of edition. Pro features such as Watermarking, Proofing, Pagination, Slideshow, and Albums add columns automatically when the relevant addons are active, without configuration.

Yes. The image view exposes one row per image with file, caption, alt text, link target, and any addon-specific fields like watermark or proofing flag. Filter by gallery to scope down, or filter by missing-field booleans to surface accessibility gaps across the entire library at once.

Yes. Albums use the envira_album CPT and bundle multiple galleries together. SleekView surfaces a per-album view with bundled gallery list, total image count, and album-level theme. Useful for portfolio sites where albums are the navigation unit and the operator needs a quick overview of bundle composition.

Yes for title, theme, and visibility. SleekView writes through Envira's own save path so any cache layer, gallery rebuild, or addon hook fires the same way it does from the plugin's UI. Long-form changes like image reordering edit best in the gallery edit screen because of the drag-and-drop UI.

Yes. Dynamic galleries (sourced from a folder, post type, or category) and EXIF galleries (built from EXIF metadata) write configuration to the same envira CPT, so SleekView surfaces them as filterable columns. The image rows continue to be generated by Envira on render; SleekView reads the configuration and the cached gallery data.

Yes. SleekView uses Envira's standard save path, so the gallery rebuild, any object cache, and any page cache layer respond to the post update the same way they would from a save in the gallery edit screen. Front-end output stays consistent with the configuration in the table.

Yes. Each subsite stores galleries in its own wp_posts and wp_postmeta, with its own table prefix, and SleekView respects that scoping. Per-subsite admins see only their galleries; network admins can switch between sites and each one renders its own gallery list independently.

Yes. Any filtered view exports to CSV from the table header, with active filters and column order respected. Useful for an accessibility audit handed to a content team, a rights-management report shared with a legal review, or a portfolio overview attached to a client onboarding email.