No. SleekView reads the existing Forge options JSON, the Bricks template content that references each Forge action, and any postmeta Bricksforge already writes. The only write is the upvote increment, which lands on a meta key you choose so it sits next to the rest of the action data row.

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 Designer, you can flip that in the view settings without touching any code.

You map a bf_review_status meta key on the synthetic action row Bricksforge maintains when you build the view. SleekView shows a colored pill for each value, and any action without a status simply renders without a pill rather than blocking the card from showing on the board at all.

Yes. SleekView reads whatever Forge has registered. Animation triggers, form actions, panel presets, and global options all surface as cards on the board, grouped by the family chip you pick during view setup without any special configuration step at all.

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 Forge Refactor queue that only Designers and Admins can see. Both views share the same data underneath.

When the action is unregistered from Forge, SleekView removes the card on the next refresh. The upvote meta is preserved on the action row for export, in case Bricksforge restores the action or you want to migrate the historical signal into a new replacement action down the line.

Yes. Every SleekView is available as a shortcode, a Gutenberg block, and a Bricks element wrapper. You can drop a Forge Refactor view onto a Design Ops page, embed a Top usage view on a planning wiki, or stitch several views into a single dashboard with separate columns side by side.

SleekView paginates and sorts at the database level rather than loading every bricks_template into memory, so a site with hundreds of Bricks templates referencing Bricksforge actions still renders the top of the feedback board in well under a second on a normal shared host with default caching enabled.