It reads what Feed Pro saves. The plugin keeps writing cached LinkedIn posts into its own table. SleekView mounts a board on top of that data, so the board renders directly from the live cache with no syncing job and no duplicate LinkedIn store to maintain on the WordPress side.

Yes. SleekView supports logged in voting scoped per role, so an editor can read the board and vote without ever reaching Feed Pro 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 curation honest without forcing a wall of approvals before each pin.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can scope the board by author, post category, or date. Different pages can show different boards, which is how most marketing teams build a campaign focused review next to the full LinkedIn cache on a separate page.

Status is a column on the cached post, so flipping it to Hidden updates that column on the live record. Most teams pair that with a small filter that respects the Hidden status when Feed Pro renders the embed, so hiding on the board actually removes the post from the LinkedIn widget.

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

Yes. Upvotes write back to the source column, which means any of your custom dashboards, scheduled cleanup jobs, or marketing reports can sort LinkedIn posts by score. Several teams use the score to pin the highest voted posts during campaign weeks, 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 columns, which means even very long LinkedIn caches stay responsive on the board without forcing the marketing team to spin up a separate cache review tool.