Both options are supported, depending on the filter you save with the board. A common setup is one board scoped to Elementor AI pages for editorial review and a second board scoped to all pages for the site admin. Filters apply on top of the kanban grouping.

Yes. SleekView renders one column per distinct value found in the grouping field, so any custom post status your team registered with register_post_status appears automatically. You can also lock the board to a fixed status set if you prefer a stable layout.

Yes when the target column is wired to the publish status. SleekView writes the new post_status to the wp_posts row in place, so any publishing hook, sitemap regeneration or notification that fires on transition_post_status runs as it would after a normal Publish click.

Yes. SleekView never touches Elementor AI's own history records, it only updates the post status on the page row. The full Elementor AI prompt history, version log and saved layouts remain available exactly as they were before the drag.

Yes when those fields are stored as post meta on the page. SleekView lets you map any meta key to the card meta line, so a card can show, for example, the page section template plus the AI model that generated the hero.

Yes. SleekView paginates inside each column and queries wp_posts with indexed status filters, so even a site with ten thousand pages loads its kanban in well under a second. Drags fire one indexed update against the primary key.

Yes. SleekView inherits the capabilities you configure on the view. A contributor role can be limited to viewing the board, an editor role can drag between draft and pending columns, and an administrator role can move cards into publish and scheduled columns.

Yes. SleekView never owns Elementor AI data. It reads and updates standard wp_posts rows in place, so deactivating SleekView only removes the kanban view, not the pages themselves. Elementor AI keeps generating pages exactly as before.