No. SleekView reads the draft rows the Writesonic Pro WordPress connector already writes to your database, so anything stored in the drafts table or the equivalent meta keys is fair game. There is no extra Writesonic seat to provision, no API token to manage, and no separate billing line.

You pick the column at setup. Most teams add an integer votes column on the drafts table or attach a meta key tied to each draft ID. SleekView reads and increments that value on click, so the editor signal survives Writesonic connector updates and plugin reactivations cleanly.

Yes. The view supports numeric filters on any column, including votes, so you can hide drafts with fewer than three upvotes once a voting window closes. Hidden drafts stay in the database for audit and can be brought back into the board with a single filter change later.

Every click runs through a SQL increment statement that is safe under concurrent writes, so two simultaneous upvotes always land as plus two and never as plus one. The card subscribes to the new count and updates in place without a full page reload, so both voters see the right total.

Yes. The board accepts manual items, which is the standard path for template requests, prompt ideas, and integration suggestions. The manual card carries the same status pill, the same category tag, and the same Upvote button as a generated draft, but it points at a manual record.

If the drafts table carries a site or workspace identifier column, SleekView can filter the view to a single site or expose a site pill so writers can switch on the fly. Each site can carry its own template palette, its own status list, and its own access rules so editorial teams stay separate.

Yes, as long as you keep the columns you mapped at setup. SleekView does not own the schema, it reads what you point it at, so a connector update that adds new columns simply gives you more fields to surface on cards. Rename a column and you remap it in the view config quickly.

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