It reads the live ones. SleekView Feedback sits on top of the Borlabs services post type and the relevant wp_postmeta rows. You map the columns once and the board renders directly from the source, so there is no syncing job, no ETL, and no duplicated consent catalog to keep in step with the live configuration on the site.

Yes. SleekView supports logged in voting for staff only views, so a legal reviewer can have a Subscriber level account that can vote on services and see the queue without ever reaching the Borlabs admin screens. Marketing leads can do the same on their side, and the board itself decides who sees what based on the role.

Logged in voters get one vote per item per user ID, and there is a rate limit per IP. There is also a per role weighting option you can enable, so a legal vote on a Compliance card can count for more than a marketing vote on the same card, which keeps the consent debate honest and prevents simple vote stacking by the bigger team.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can scope the board to a specific group, a specific status, or a specific service type. Different pages can show different boards, which is how most consent teams build a marketing only view alongside the all services view that lives on the main page.

Status is a column on the source post or meta row, so retiring a service on the board updates that column on the live record. Most teams pair that with a small filter that respects the Retired status when Borlabs renders services on the front end, so retiring a service on the board genuinely stops the script from loading.

Yes. SleekView lets you flip the same data source between anonymous and logged in modes on different pages. A staff intranet can show the full service history and votes, while a public consent register can show only the service, the consent group, and the current status without exposing internal votes or notes from the team.

It writes back to the source column, which means any custom Borlabs dashboards, scheduled cleanup jobs, or compliance reports can sort services by score. Several teams use the score to gate which services land in the quarterly consent register, which makes the board operational rather than a vanity counter next to the Borlabs admin.

The view paginates server side and only loads the rows it needs to render the current page. SleekView uses any indexes you provide on the vote, status, and timestamp columns, which means even multi year Borlabs catalogs stay responsive on the board without forcing the consent team to spin up a separate review tool just for the cookie banner config.