Either works. SleekView reads any Ultimate Member form by ID and shows every field in the data source picker so you can choose which one stores the vote, the status, and the category. An existing Suggestions form just needs a numeric upvote field added inside the Ultimate Member form builder to become a board source.

Yes. The SleekView block respects whatever access rules the parent page has. Put the block on an Ultimate Member dashboard page restricted to the Premium role and the board only loads for logged-in Premium members. Add a role check to the data query to also restrict which submissions appear inside the board.

SleekView stores a per-user vote record in its own usermeta key, so the same Ultimate Member account cannot upvote the same submission twice. The vote count on the parent submission still increments by one per unique member, and the per-user record lets the board show a different button state for already-voted items on every render.

No. SleekView reads Ultimate Member data, it does not own it. Every submission, role assignment, and form field continues to live in usermeta and the standard Ultimate Member tables. Deactivating the SleekView plugin removes the board from the page but leaves the underlying suggestions untouched and fully editable in the Ultimate Member admin.

Yes. The query builder accepts a role filter, so you can build a board that only shows submissions from Premium members, only from Free members, or any combination of roles. The role filter uses the standard Ultimate Member um_roles meta, so a member who is later upgraded to a new role appears on the new board automatically.

Yes. Those extensions store their data in standard WordPress tables that SleekView can read alongside the user meta. A board scoped to a single Ultimate Member group only shows submissions from group members, and friend connections can be used to weight the vote count if the site wants to surface suggestions popular inside a member's network.

Guest voting is off by default because it does not write back to a real Ultimate Member user. You can enable a session-based guest vote that stores anonymous clicks in a SleekView vote table and merges them on the next login, which is useful for marketing pages that want to capture interest before forcing a signup.

Submissions from a deleted account stay on the board as anonymous cards by default because the vote count still represents real community interest. Admins can choose to soft-hide submissions from deleted accounts entirely, which is the safer option for GDPR cleanups when a member exercises their right to be forgotten.