SleekView reads ImagineAI data straight from the WordPress database, so any plan that writes rows to the standard tables works. Plan differences only affect what the ImagineAI API returns, not how SleekView groups the rows or renders the kanban on the screen.

By default a drop only updates the job_status column. You can extend it with a hook that calls wp_update_post or similar when a card lands in a chosen lane, but SleekView keeps the two actions separate so accidental drags never push anything live without explicit confirmation from a human.

Yes. SleekView views are configuration only, so you can build one board filtered to one slice and another to a different slice from the same ImagineAI table. Each user picks their default board, and admins can pin shared boards to the WordPress admin sidebar for the team.

SleekView reads distinct status values on every load, so any new status shows up automatically as its own lane at the end of the board. You can drag the lane into position, assign a color, and pick which fields its cards should surface, without rebuilding the view from scratch.

No. The drag handler updates the same job_status field that the ImagineAI admin screen would update, so the next worker tick sees the new state and handles retries, sync, and any linked post updates exactly as it would if a human clicked the status dropdown manually on the row.

SleekView respects WordPress capabilities, so you can require publish_posts or a custom capability before a card can land in a given column. People still see the lane and can scroll it, but the drop target rejects their card with an inline message instead of silently failing.

Each lane uses a virtual scroller, so a column with five hundred rows still renders fast and stays responsive on a laptop. The lane header shows the exact count, and the filter bar at the top narrows large lanes without resetting the scroll position or any pending card.

SleekView reads and writes the existing ImagineAI tables and never adds shadow tables for the source data. View configuration sits in its own small options table, so uninstalling SleekView leaves your ImagineAI rows untouched and your pipeline exactly where it was before.