It reads what Monarch saves. The plugin keeps writing share location settings into options and per page meta. SleekView mounts a board on top of that data, so the board renders directly from the live Monarch config with no syncing job and no duplicate settings store to maintain on the site.

Yes. SleekView supports logged in voting scoped per role, so an editor can read the board and vote without ever reaching Monarch settings. Senior marketing leads keep full admin, junior editors see a curated view, and the same data source backs both surfaces without extra code on top.

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, so a UX vote on a Popup card can count for more than a marketing vote on the same card, which keeps the share location debate honest on contentious cards.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can scope the board by share style, status, or post type. Different pages can show different boards, which is how most teams build a focused review of broken popups next to the full Monarch review on a separate page.

Status is a meta key on the location, so flipping it to Retired updates that key on the live record. Most teams pair that with a small filter that respects the Retired status when Monarch renders share locations, so retiring on the board actually removes the location from the page on the next render.

Yes. SleekView lets you flip the same data source between anonymous and logged in modes on different pages. A staff intranet can show full location history and votes, while a public log can show only the location, share style, and status without exposing internal team notes.

Yes. Upvotes write back to the source meta key, which means any of your custom dashboards, scheduled cleanup jobs, or marketing reports can sort share locations by score. The board is not a vanity counter, it is the input to whatever cleanup logic you choose to run against the Monarch share config.

The view paginates server side and only loads rows it needs to render the current page. SleekView uses any indexes on the vote, status, and timestamp meta keys, which means even large Monarch configs stay responsive on the board without forcing the marketing team to spin up a separate review tool just for share locations.