No. The view reads chat or job rows live from the existing AI Engine Pro tables like wp_aiengine_chats and writes upvote counts back into the same row, so there is no second database, no sync queue, and no risk of the board drifting out of step with the plugin admin.

Yes. Each board has a visibility setting, public, logged in users only, or members of specific roles. Public boards still respect rate limiting per IP, and logged in boards tie votes to user IDs so duplicates are blocked at the source.

The vote increments the numeric column you picked in the view config on the matching AI Engine Pro row inside wp_aiengine_chats. There is no API round trip to a SaaS service, no queue, and no delayed write. Every other report or export that already reads that column sees the new count immediately.

Yes. SleekView ships four render surfaces, Table, Charts, Kanban, and Feedback. The same underlying AI Engine Pro data source can be wired to multiple views with different filters and field mappings, so one board feeds the public roadmap, another feeds internal triage, and another feeds reporting.

Each distinct status value or category value gets mapped to one of six color presets, blue, violet, emerald, amber, rose, and cyan. The mapping is set once in the view config and applied consistently across the board, so brand palettes stay coherent and no custom CSS is needed.

SleekView reads the schema on every page load and re-detects columns automatically. If AI Engine Pro renames a column or adds a new status value, the view picks up the change without manual remapping.

Both. Anonymous voting uses an IP and cookie based fingerprint with a rate limit per board, and logged in voting ties the upvote to the WordPress user ID. The setting is per board, so a public roadmap can stay anonymous while an internal triage board requires login.

SleekView paginates results and caches the sorted vote order, so boards comfortably handle tens of thousands of chat or job rows with sub second loads on a standard WordPress host. Filters run server side against the same indexes AI Engine Pro already uses, so adding categories or statuses does not change the performance prof...