Yes. The plugin registers closed as a real WordPress post status, and SleekView picks it up automatically when you choose post_status as the grouping field. You get Draft, Pending, Published, and Closed columns without any configuration, and any custom status added by a child theme or extension shows up the same way.

Yes. The plugin stores departments in the jobpost_category taxonomy, and SleekView surfaces taxonomy terms as a card field. You can show the primary department under the job title, or use it to drive the card border color so engineering, marketing, and operations roles are visually distinct at a glance even when the board is filtered to all departments.

SleekView writes post_status to closed through wp_update_post. The standard transition_post_status hook fires, the plugin's frontend stops showing the role in active listings, and the post meta history records who closed it and when. The Closed column is one-way by default so positions cannot accidentally drag back into Published; reopening uses an explicit card action.

Yes. Because every move goes through wp_update_post rather than a direct database write, the standard transition_post_status and save_post hooks fire just like a manual save in the admin editor. The plugin's hiring manager notification, any third-party Slack notifier, and the rewrite cache invalidation all run exactly as if you had pressed Publish from the post screen.

Yes. Simple Job Board stores location and salary in postmeta with keys like jobpost_location and jobpost_salary. SleekView lets you pick any postmeta key as a card field, format it (currency, location string, dates), and show it next to the job title. A common card face shows title, department, location, and closing date in that order.

It surfaces the closing date as a card field and lets you sort the Published column by it. The actual transition to Closed is handled by the plugin's own scheduled task, so SleekView reflects the new status the next time the board renders. You can manually drag a role into Closed earlier if a position fills before its scheduled close date.

Yes. The SleekView filter bar reads the same taxonomies the plugin already registers, plus any postmeta keys you mark as filterable. Hiring leads can pin the board to Engineering, Operations, or a specific city, and the filter persists per user so each manager opens straight to their own pipeline without redoing the filter every time.

Yes. SleekView honors the same edit_post and edit_published_posts capabilities the WordPress posts screen uses for the jobpost type. Users without permission to publish see the Published column but the drag handle is disabled on cards they cannot edit. Combined with the plugin's recruiter and admin role separation, the board enforces the exact same access rules as the standard admin.