Yes. Moving a card calls wp_update_post with the new post_status, the same function the editor uses on publish, so transition_post_status, publish_{post_type}, and any custom code listening to the standard WordPress hooks continue to fire without extra plugin glue.

SleekView reads any CPT UI registered post type through standard WP_Query, including assigned taxonomy terms and registered post meta. You pick the source, choose post_status or a taxonomy term to group by, and SleekView renders one card per record with the fields you select.

Yes. SleekView ships with role-based permissions, so record owners can have a single page that holds the review board and nothing else. Only chosen roles can drag cards, and destination columns can be limited per role so contributors cannot move records into Published without an editor.

Derived states are first-class in SleekView. You can define a workflow_state computed from several fields, such as treating a record as Pending when a custom approval flag is false and the post_status is draft, and SleekView groups records by that derived value across the columns.

Each board has one source so the rules stay clear, but most setups run one board per CPT UI post type on the same editor dashboard. Column counts at the top of each show waiting work at a glance, so the team sees case studies and projects without losing model boundaries.

Dragging never deletes data. It calls wp_update_post with the new post_status, which is the same thing a publish in the editor does. Other fields, taxonomy terms, and post meta are not touched, so all record values remain exactly as saved before the column change happened.

Yes. Each card can show the time since the record was last modified or since post_status was last changed, so a record stuck in Pending for a week looks visibly different from a fresh one. Sort options can place the oldest cards at the top of every column to keep stale work visible.

No. SleekView pages the board, only loads cards for visible columns, and uses the indexed wp_posts table for queries. Sites with hundreds of thousands of CPT UI records stay responsive because heavy post meta is only fetched for cards currently on screen during review.