Yes. SleekView calls wp_update_post with the new status so the change goes through the standard WordPress API. That means transition_post_status hooks fire, the audit trail records the move, and any plugin or theme that listens for status changes (including WP Job Manager's own email notification system) reacts exactly as if a human edited the post in the admin.

WP Job Manager stores Filled as a _filled postmeta value rather than a real post status, so SleekView treats Filled as a virtual column. Dragging a card into Filled writes _filled = 1 and keeps post_status as publish so the listing still resolves on the careers page, just with the Filled label that the plugin's frontend already shows.

Yes. SleekView reads the _featured postmeta value the plugin sets when an employer pays for a featured slot. You can map that to a corner badge on the card, a colored border, or a separate Featured swimlane. Dragging a card in or out of the swimlane updates the postmeta, so the listing instantly gains or loses its featured placement on the public job board.

It will. The plugin uses a WP-Cron task to flip jobs to the expired status once they pass their _job_expires date. SleekView surfaces expired listings in their own column but does not let you drag them out, because that would conflict with the scheduled task. You can republish from the card menu, which writes a fresh expiry date and moves the listing to Approved.

Yes. SleekView writes each move as an atomic post update with optimistic concurrency. If two recruiters move the same card at the same time, the second move sees the new status and re-renders the column. The card highlights for a moment so the second person knows someone else acted first, and no work gets silently lost.

It does. The Employer Listings add-on stores each company as its own post type with submissions attached, and SleekView treats those exactly the same way. You can build a separate board grouped by employer approval status, or filter the job board to one employer using the same postmeta queries the add-on already exposes through the plugin's API.

If the WC Paid Listings add-on is active, SleekView detects the extra post statuses it registers (including pending_payment) and lets you add them as columns alongside the core ones. Moving a card out of pending_payment is read-only because the status is set by the payment gateway, but you can drag it from publish back to pending if you need to pull a listing for review.

Yes. SleekView honors the capability the plugin already uses for editing a job_listing. If a user has read access but not edit_job_listing, they see the cards but the drag handle is disabled. Combined with the standard WP Job Manager Employer dashboard, you can give employers a read-only view of their own listings while keeping recruiter actions on the moderator board.