Yes. SleekView reads wp_userfeedback_responses directly, and the response schema is identical between the Lite build and the Pro tiers. Every column SleekView relies on, including survey ID, question ID, and answer text, is present in both editions, which means the board renders the same way regardless of which tier you have installed.

Yes. A board scope can filter by a public-or-private meta key, so a public roadmap page only shows responses marked as safe to surface. Editors keep a separate internal board that shows every response, including ones flagged as sensitive, account-specific, or still awaiting a privacy review by the customer success team.

Team upvotes write to one meta key, restricted to logged in editors. Public upvotes write to a different meta key, available to any visitor or only logged in members depending on your setting. The board combines both with a configurable weight, so the final rank reflects both internal priority and external demand transparently.

The board is most useful for open text responses where each answer is unique, but it works for multiple choice too. For multi choice surveys, SleekView can group responses by the selected option, count each group, and show one card per option ranked by frequency, with status pills tracking which options the team is acting on.

Yes. The SleekView toolbar includes a CSV export that respects the current filter, so you can pull every Planned response from a single survey, every Open response from a date range, or any other slice into a spreadsheet in one click. The export carries answer text, upvote totals, statuses, and survey context.

By default SleekView writes to its own meta key so a status field always exists even when UserFeedback does not provide one natively. You can also point SleekView at an existing meta key, in which case the side panel writes to that field and every report or workflow built on it picks up the new value.

Yes. A board scope can include or exclude any status value, so a forward-looking public roadmap shows only Open, Reviewing, and Planned responses. You can then publish a separate Shipped board that highlights what has already gone live, giving customers a clear sense of progress over time.

Yes. SleekView never owns UserFeedback data, it only reads from and writes to the response tables and meta keys. Removing SleekView leaves every response, vote, and status field exactly where UserFeedback expects them, so the default responses table keeps working with no rebuild or data migration step required.