No, but you can. SleekView Feedback works with any post type, including one you already use for suggestions, requests, or roadmap items. You can also spin up a new post type called Suggestions in under a minute. Either way you bind the vote, status, and category columns once and the board picks up new posts automatically.

On every request, SleekView calls the official WishList functions that return the current user's active levels and status. There is no cached token and no sync window. If a member is cancelled, their write access disappears on the next page render, and if a level upgrades, the corresponding board access turns on immediately.

Yes. Every Feedback view block has its own access rules, so you can run a public read only board, a paid level board, and a top tier private board side by side. Each board uses its own source post type and its own list of allowed WishList levels for read, post, and vote actions, with no conflicts between boards.

Past votes stay attached to the cards so the roadmap signal is preserved. The member loses the ability to add new votes or post new ideas on boards they no longer qualify for. If they renew or upgrade later, all rights come back the moment WishList marks the status active again, with no manual reset needed.

Yes. Each board has its own list of public statuses. You can show Open, Planned, and Shipped to members while keeping In progress and Declined for the admin view only. The status column on the source row stays the truth, and SleekView only renders the statuses you allow on the public board.

It feels native. The Feedback view renders as semantic HTML using your theme styles, so cards inherit your fonts, colors, and spacing without iframes or vendor scripts. Members see your brand on every card, every status change, and every upvote, which keeps trust high and avoids the brand whiplash of a third party tool.

Yes. Status changes fire a WordPress action that any notification plugin or custom code can listen for. Many WishList sites use this to email the original poster plus every upvoter, which doubles as a re-engagement nudge and shows your members that requests actually turn into shipped features over time.

No. SleekView caches query results and only re-queries on vote or status change. The block is lazy loaded so it does not block initial paint. There are no third party requests for fonts, analytics, or scripts, so Core Web Vitals stay healthy even on dashboards loaded with drip protected content and active members.