No. SleekView reads the draft rows the LongShot AI WordPress connector already saves to your database, so anything stored in the drafts table or its meta keys is fair game. There is no extra LongShot seat to provision, no API token to manage, and no separate billing line to pay later.

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 LongShot connector updates and plugin reactivations and cache flushes.

Yes. If the fact-check score lives on the same row or in a referenced meta key, SleekView can surface it as a numeric badge on the card next to the editor vote count. Editors can sort by either signal independently, or by a weighted sum so consensus drafts rise to the top of the board.

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 fact-check flags, template requests, and integration ideas. The card carries the same status pill, the same category tag, and the same Upvote button as a real draft row, but it points at a manual record you define.

If the drafts table carries a brand or workspace identifier column, SleekView can filter the view to a single brand or expose a brand pill so editors can switch on the fly. Each brand can carry its own content type palette, its own status list, and its own access rules so 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 editor role read access. Editors see the cards, vote on drafts and fact-check flags, and post template requests through that page without ever loading the WordPress admin or touching the full surface.