No. SleekView reads the suggestion rows your existing Wordtune WordPress connector already saves locally, so anything stored in the suggestions table or its meta keys is fair game. There is no second SaaS account to provision, no extra API token to manage, and no separate billing line.

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

Yes. The view supports numeric filters on any column, including votes, so you can hide suggestions with fewer than three upvotes once a voting window closes. Hidden suggestions 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 mode requests, tone preset ideas, and integration suggestions. The card carries the same status pill, the same category tag, and the same Upvote button as a real suggestion, but it points at a manual record.

If the suggestions table carries a site or brand identifier column, SleekView can filter the view to a single site or expose a site pill so editors can switch on the fly. Each site can carry its own mode 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 editor role read access. Editors see the cards, vote on suggestions, and post mode requests through that page without ever loading the WordPress admin or touching the editor surface for the whole team.