No. SleekView Feedback reads the envira post type and image meta that Envira Gallery Pro already writes. There is no separate roadmap table, no sync job, and nothing to migrate. Upvotes are stored as numeric meta on the same row your Envira Pro stats chart against, so totals stay aligned across surfaces.

Yes. The Feedback view inherits the same query filters as SleekView Tables and Charts. You can restrict by gallery status, album, layout, review state, or any custom meta. Most Envira teams expose only galleries tagged Roadmap or Bug with statuses Planned, In progress, and Shipped on the public board and keep drafts hidden.

SleekView tracks upvotes per browser through a signed cookie and per user ID for logged-in WordPress users. You can also require an account before voting if you want stricter dedupe. Vote totals stay consistent across page loads and devices for known users, with cookie-based dedupe protecting anonymous voters from double counting.

A separate roadmap tool is a different product with its own database, login, and pricing. You sync galleries across, then maintain two sources of truth. SleekView Feedback reads Envira data live through WordPress, so the board, the album list, and the Envira admin always show the same numbers. There is one source of truth.

Yes. Any numeric meta key can act as the vote column, any taxonomy or text meta can be the status, and any taxonomy or meta can be the category. The SleekView block exposes a dropdown for each role so you map the Envira columns once through the block UI and never touch the underlying template to change which fields render.

By default upvotes update the meta silently to avoid spamming busy editors. You can opt in to firing a standard WordPress action on each upvote that you bridge into Slack or email if you want owners to see live demand, or threshold it to alerts every ten or fifty votes for a calmer notification cadence.

Yes. SleekView lets you scope the query to one or many terms in any taxonomy, so you can run a board per album, per layout, or per editor. Each board is a separate block on a separate page, all reading from the same underlying Envira store with their own filter and column mapping configured.

Because SleekView Feedback reads whatever query you point it at, you can swap the source from envira to a different post type or table without rebuilding the board. The cards, badges, votes, and filters stay intact. You re-map the column roles in the block settings, and the URL stays the same for visitors and search engines alike.