Directorist stores expired state in a _listing_status postmeta value rather than registering a custom post status. SleekView reads that postmeta and surfaces it as a virtual Expired column, which means listings the plugin's scheduled task has expired appear in their own swimlane without any schema change. The column is read-only by default; you can renew from the card menu.

Yes. Status changes go through wp_update_post, which fires the standard transition_post_status hook. Directorist listens on that hook to send its listing approval email to the owner. Any third-party Slack notifier, audit log plugin, or sitemap regenerator also runs exactly as if the moderator had opened the listing and pressed Update in the admin editor.

Yes. If the Directorist Pricing Plans add-on is active, each listing has a _fm_plans postmeta value pointing to the assigned plan. SleekView surfaces that plan name as a card field and can drive a corner accent color, so Premium and Basic listings are visually distinct on the board without changing how the plugin stores the data.

Yes. Both at_biz_dir-category and at_biz_dir-location are exposed as filterable card fields and as optional column titles. You can pin the board to one category, one city, or both, and the filter persists per user. Combined with grouping by post_status, this gives each moderator their own focused workspace.

SleekView writes the _featured postmeta value to 1, which is exactly what the plugin does when an admin toggles Featured inside the listing editor. The Directorist frontend immediately treats the listing as featured, applying the featured badge, sorting it to the top of category pages, and including it in the homepage featured carousel.

Yes. SleekView respects the same edit_at_biz_dir and edit_published_at_biz_dirs capabilities the plugin already uses. Users without permission see the cards but the drag handle is disabled. Combined with Directorist's role separation between authors and moderators, the board enforces the exact same access rules as the standard admin without any extra configuration.

Yes. The renew action on a card menu calls the same renewal workflow the plugin's frontend uses, which writes a new _expiry_date postmeta value and clears the _listing_status. The card moves from Expired to Published, the listing reappears in the public directory, and Directorist's renewal-paid email fires through the standard hook.

Yes. SleekView paginates each column independently and lazy-loads as you scroll, so a directory with ten thousand active 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, and Expired is collapsed by default so it does not slow the working board.