No. SleekView reads the copper_opportunity CPT that Copper CRM for WordPress mirrors locally, and any upvote increment lands on a WordPress postmeta key. Status pill edits update the stage id meta, which the Copper CRM for WordPress connector can mirror back during the next sync cycle.

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 Stakeholder, you can flip that in the view settings without touching any code at all on the WordPress site.

You map the synced Copper stage id as the status pill source when you build the view. SleekView shows a colored pill for each value, and any opportunity without a stage simply renders without a pill rather than blocking the card from showing on the board at all in public.

Yes. SleekView reads whatever Copper CRM for WordPress has mirrored. Multiple pipelines, multiple Copper accounts, and archived pipelines can be filtered into separate saved views, so a marketing page can show one pipeline and a sales page can show another without conflicts.

Yes. Every saved view has its own role and capability scope, so you can publish a public client feedback board on an agency page and a separate internal triage queue that only PMs and Admins can see. Both views share the same Copper data underneath.

When the underlying copper_opportunity record is removed by the next sync, SleekView removes the card on the next refresh. If the opportunity is archived rather than deleted, the card disappears from the public view but the upvote meta is preserved on the archived row for history.

Yes. SleekView views render as shortcodes, Gutenberg blocks, and short HTML snippets. Most agencies drop a Top votes view scoped to a single client pipeline inside a password-protected portal page so clients see the upvote board without needing a Copper seat at all today.

SleekView paginates and sorts at the database level rather than loading every copper_opportunity into memory, so a sync history with thousands of synced opportunities still renders the top of the feedback board in well under a second on a normal shared host with caching enabled.