It reads the listing_status postmeta from every property in the impress_listing post type and builds one column per distinct value. The plugin's default values (Active, Pending, Sold, Off Market) appear out of the box. Any custom status added by an MLS feed or by an office workflow shows up automatically the next time a card with that status is loaded.

Indirectly. SleekView's drag actions fire the impress_listing_status_changed hook the plugin already uses to mark its MLS export feeds dirty. Whatever MLS sync the office has configured (MLS RETS, RESO Web API, or a custom feed) runs on its next scheduled cycle and picks up the updated status without any manual intervention or extra integration work.

Yes. IMPress stores the assigned agent in the listing_agent postmeta, and SleekView lets you filter the board by that field. Agents open the board pinned to their own assignments, brokers see the full portfolio, and the same filter persists per user. Combined with the plugin's role capabilities, agents cannot edit listings they are not assigned to.

SleekView writes listing_status back to Active and fires the impress_listing_status_changed action. The plugin's MLS feed re-marks the listing as Active on the next sync. The card history records the move and the reason if you choose to provide one, so the audit trail accurately reflects what happened in case the brokerage needs to review a transaction later.

Yes. Days-on-market is calculated from the property's listing date postmeta and the current date. SleekView shows it as a corner badge with a warning color past the office threshold (commonly 60 or 90 days). Sort the Active column by days-on-market and the longest-standing listings rise to the top, making price reduction conversations much easier to prioritize.

Yes. SleekView honors the same edit_impress_listing and edit_published_impress_listings capabilities the plugin already uses. Agents without permission see the cards but the drag handle is disabled, and the Sold and Off Market columns enforce extra capability checks because they are write-protected. The board mirrors exactly what brokerages already configure on the standard admin.

Yes. The plugin's IDX search rebuilds its index when a listing's status or core fields change. Drag actions go through the standard write path, fire save_post, and trigger the IDX rebuild on the next scheduled cycle. Brokerages running IDX search on their public site do not need to do anything extra; the search results stay in sync with the board.

Yes. SleekView reads the WordPress featured image set on each impress_listing post and uses it as the card cover. The address, price, and beds/baths line display underneath, so the board doubles as a visual portfolio. For brokerages with consistent listing photography, the visual cue makes it much faster to locate a specific property than reading addresses.