Yes. Upvotes increment the meta key you picked as the vote column on the original feedback row. There is no parallel votes table, no external service, and any reports or exports you already run against your PeepSo Pro data pick up the new counts as soon as each vote is cast on the board by a member.

Yes. The submit button opens the form you choose, posts the new idea into the same source table the board reads, and shows it on the board with zero votes and the default status. Members never see a separate submission form or a parallel database to sign in to at any point during the flow.

Boards respect the same PeepSo and WordPress role rules the rest of your site uses. Cards from a private context only appear for members who can already read that context, and the same role checks gate who can vote, comment, or submit a new idea about how the community should behave.

Yes. Each board is its own SleekView render scoped to a chosen source, so you can run a dedicated PeepSo board, a separate forum board, and a third for sitewide ideas. Vote counts and status badges are independent per board, so a vote on one does not affect any of the others on the site.

Cards stay on the board because the data lives on the feedback row, not on the deleted member record. The author display name shifts to a generic deleted account label, the vote count is preserved, and the status stays whatever the admin team last set, so the public history of the request is not lost.

Yes. Any post taxonomy or meta key can drive the category tag on each card. Most teams use a small set like Feature request, Bug, UX, and Question, with one color per category, so members can scan the board and filter to the kind of work they are most interested in voting on right now.

Yes. SleekView ships with role-based permissions, so you can let logged in members vote, restrict submissions to paying members, or open both to everyone. Limits are checked on the server side so the rules cannot be bypassed by editing the page or replaying the request from a separate tab.

Yes. SleekView pages the board, only loads the cards on screen, and uses indexed columns for the vote and status filters. Communities with millions of activity rows stay responsive because the heavy fields are only fetched for the feedback cards the visitor is actually looking at on the current page.