SleekView reads School Pro data directly from the WordPress database, so any version that writes posts and meta to the standard tables works. The free build and every premium tier expose the same schema, which means the feedback board renders the same way regardless of which School Pro plan you run.

Yes. Voting uses the front end SleekView shortcode, so any signed in subscriber, student, or parent can click the upvote button without ever seeing wp-admin. Capabilities drive what each role can do, and you can lock the board down to specific cohorts or to a specific membership level.

Votes live in the source row, either as a meta field or a column you nominate, so every standard School Pro export, backup, or migration carries them along. Updates to the plugin never touch the vote column unless you explicitly map it to a field School Pro starts using directly.

Yes. SleekView views are configuration only, so the same School Pro dataset can power a feedback board for students, a kanban for staff working the requests, a table for the deep dive admins, and a chart for the principal. Every surface reads and writes the same rows.

SleekView records one vote per signed in user per item by default, so a second click toggles the vote off rather than inflating the count. Anonymous voting is available for public schools that want guest input, with optional IP based rate limiting to keep the totals honest.

Yes. Each card opens a detail panel with the full description plus a comment thread powered by the standard WordPress comments table. Staff replies are flagged as official, and email notifications use whichever transactional mail layer your School Pro install already has wired up.

Yes. SleekView reads the active membership level on the request and can filter visible items per role. A common setup hides Planned and Shipped from free accounts while showing the full roadmap to paid members, mirroring how Canny Internal and Public boards behave.

SleekView paginates results, indexes the vote column on first load, and caches rendered cards through the standard WordPress object cache. A board of ten thousand items with a thousand active voters renders well under a second on shared hosting, and votes use a single targeted SQL update.