It reads what AddToAny saves. The plugin keeps writing share settings into wp_postmeta and global options. SleekView mounts a board on top of that data, so the board renders directly from the live share config with no syncing job and no duplicate share catalog 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 AddToAny 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 senior marketing vote can count for more than a junior editor vote, which keeps the share debate honest without forcing a wall of approvals.

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

Status is a meta key on the page, so flipping it to Disabled updates that key on the live record. Most teams pair that with a small filter that respects the Disabled status when AddToAny decides to render, so disabling on the board actually hides the share row on the page.

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 share row history and votes, while a public log can show only the page, status, and category without exposing internal team notes.

Yes. Upvotes write back to the source meta key, which means any of your custom reports, scheduled digests, or marketing dashboards can sort pages by score. Several teams use the score to gate which pages land in the weekly review, which makes the board operational rather than a vanity counter.

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 editorial catalogs stay responsive on the board without forcing the marketing team to spin up a separate review tool.