No. SleekView reads the existing dipi_cpt_overlay posts and the wp_postmeta values that Divi Overlays already writes for triggers, frequency caps, and targeting rules. The only write is the upvote increment, which lands on a meta key you choose so it sits next to the overlay data.

Yes. The Upvote button supports guest votes with a per-IP and per-session lock to keep counts honest. If you would rather restrict votes to logged-in users or specific roles like Editor or Marketer, you can flip that in the view settings without touching any code or Divi Overlays permissions.

You map a dipi_review_status meta key on the overlay post when you build the view. SleekView shows a colored pill for each value, and any overlay without a status simply renders without a pill rather than blocking the card from showing on the board at all.

Yes. SleekView reads whatever Divi Overlays has registered. Exit intent, scroll percentage, click selector, timed delay, and load triggers all show up on the cards as chips so the board surfaces them alongside each other without any special configuration.

Yes. Every saved view has its own role and capability scope, so you can publish a public Content Ops feedback wall on an editorial page and a separate Growth Refactor queue that only Growth Leads and Admins can see. Both views share the same data underneath.

When the underlying dipi_cpt_overlay post is deleted, SleekView removes the card on the next refresh. If the overlay is trashed rather than fully deleted, the card disappears from the public view but the upvote meta is preserved on the trashed post in case you restore it.

Yes. Every SleekView is available as a shortcode, a Gutenberg block, and a Divi module wrapper. You can drop a Needs refactor view onto a Growth Ops page, embed a Top converting view on a planning wiki, or stitch several views into a single dashboard with separate columns.

SleekView paginates and sorts at the database level rather than loading every dipi_cpt_overlay into memory, so a site with hundreds of overlays still renders the top of the feedback board in well under a second on a normal shared host. Aggregation queries hit indexed columns by default.