Yes. Estatik stores a listing type postmeta key that flags each listing as Sale or Rent, and SleekView surfaces it as a corner badge on the card. The price field also adapts: sales show total list price, rentals show monthly rent. A brokerage that handles both types runs the entire portfolio on one board without confusing the two transaction patterns.

It reads listing_status from every property in the estatik_property post type and builds one column per distinct value. The plugin's default statuses (Active, Pending, Sold, Rented, Off Market) appear out of the box. Custom statuses added through the Estatik settings show up automatically the next time a card with that status loads onto the board.

Indirectly. SleekView's drag actions write listing_status through wp_update_post and fire save_post_estatik_property. Whatever MLS sync the office has configured (MLS RETS or a custom feed) runs on its next scheduled cycle and picks up the updated status without any manual feed regeneration or extra integration code.

Yes. Estatik stores the assigned agent in the es_property_agent postmeta, and SleekView filters the board by that field. Agents open the board pinned to their listings, brokers see the full portfolio, and the same filter persists per user. Combined with capability checks, agents cannot edit unassigned listings even if they can see them on a shared board.

The Sold column is write-protected by default, so a direct drag is blocked. The Reopen card menu action prompts for a reason (contract fell through, finance fell over), writes the reason into the property's history postmeta, and then moves the card back to Active. The MLS feed regenerates on its next cycle so external portals reflect the change.

Yes. Days-on-market comes from the listing date postmeta and shows as a corner badge with a warning color past the office target. Listing type (Sale or Rent) shows as the other corner badge. The board can carry two corner badges per card without crowding the address, price, and beds/baths line that the board uses to identify properties.

Yes. SleekView honors the same edit_estatik_property and edit_published_estatik_propertys capabilities the plugin already uses. Agents without permission see the cards but the drag handle is disabled, and write-protected columns enforce extra capability checks. The board mirrors the access rules the office already configures on the standard WordPress admin.

Yes. SleekView paginates each column independently and lazy-loads as you scroll, so a brokerage with five thousand active and historic listings renders the visible board in well under a second. The database query is a single indexed lookup against wp_posts and the postmeta join, with Sold or Rented and Off Market collapsed by default to keep the active board fast.