No. It reads the existing property CPT and its postmeta, and saves through the standard post API. WP-Property continues to own the data definition, the front-end templates, and the search integrations. SleekView's role is purely on the read-and-edit side, which means uninstalling it leaves all your listings exactly as they were.

Yes. Any meta key can be exposed as a sortable, editable column, including MLS ID, RETS-imported fields, custom commission splits, or office-specific tags. For agencies that import via RETS daily, the same fields the import populates become directly editable in the grid for the rare cases where a manual override is needed.

No. Thumbnails render lazily and the row list is virtualized, which means a portfolio with thousands of listings, each with a photo column, still scrolls smoothly. The browser only loads the images currently in the viewport, and the next batch loads as the user scrolls. There is no preload step that causes a hang on the initial render.

Yes. Per-user row scoping uses post author or a custom assignment field. For agencies where listings are owned by an office and assigned to multiple agents, a custom assignment meta key drives the scope, so a co-listed property appears in both agents' views without duplicating the underlying record.

Yes. Any taxonomy term on the property post can drive filters and views. WP-Property's flexible type system, where Houses, Condos, and Lofts are all property types, becomes a multi-select filter at the top of the grid. Custom property types your agency adds appear automatically the next time the grid refreshes.

Yes. SleekView talks to standard post and meta APIs, not internal WP-Property functions. The major active forks of WP-Property all preserve the property CPT and postmeta layout, so the grid works against them with no special configuration. If a fork ever changes the CPT slug, that becomes a one-line config change on the SleekView side.

Yes. Filter to listings past their expiration date, select all matching rows, and bulk change status to Expired or Sold. Each update routes through the standard post API, so any plugin listening for status changes, like a sitemap regenerator or a CRM sync, fires correctly for every row.

The featured image renders as a thumbnail column. Full galleries are not edited in the grid, since image management is a different shape of work and WP-Property's media tools handle it well. The grid links each row to the standard editor where gallery edits happen, so the workflow remains coherent.