No. SleekView reads the WordHero tables already running on your WordPress site, so anything stored in wp_wordhero_generations or the equivalent meta keys is fair game. There is no second SaaS account to provision and no separate billing line, because reads and writes happen against your existing database.

You pick the column when you configure the view. Most teams add a small integer column called votes to the generations table, or use a custom meta key tied to each generation ID. SleekView increments that value on click and reads from it on render, so the count survives plugin updates.

Yes. SleekView respects WordPress capabilities, so you can let editors and authors vote while restricting the Upvote button for subscribers, or invert that and let only the content lead vote during a triage round. Status pill changes have their own capability so writers can vote safely.

Every click goes through a SQL increment statement safe under concurrent writes, so two simultaneous upvotes always land as a plus two and never as a plus one. The card on screen subscribes to the new count and updates in place without a full page reload.

Yes. The same board accepts manual items, which is how most teams handle template requests and tone preset ideas. The card carries the same status pill, category tag, and Upvote button as a generation row, but it points at a manual entry in your custom table or a simple WordPress post type.

Yes. If your install separates generations by workspace through a workspace column on each row, SleekView can filter the view to a single workspace or expose a workspace pill so users can switch. Each workspace can have its own status palette and its own access rules.

Yes, as long as you keep the chosen vote and status columns. SleekView does not own the schema, it reads what you point it at, so a WordHero update that adds new columns simply gives you more fields to surface on the card. Rename a column and you remap it in the view config.

Place the SleekView block on a private page behind a login wall and grant the writer role read access to the view. Writers see the cards, vote, and post new template requests through that page without ever loading the WordPress admin. Editors keep the admin route for status changes.