No. SleekView reads the asana_task CPT that Asana for WordPress mirrors locally, and any upvote increment lands on a WordPress postmeta key. Status pill edits update the Asana section gid postmeta, which the Asana for WordPress connector can choose to 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 site.

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

Yes. SleekView reads whatever Asana for WordPress has mirrored. Multiple projects, multiple workspaces, and even archived projects can be filtered into separate saved views, so a marketing page can show one project and a support page can show another without conflicting chips.

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 Asana data underneath.

When the underlying asana_task record is removed by the next sync, SleekView removes the card on the next refresh. If the task is archived rather than deleted, the card disappears from the public view but the upvote meta is preserved on the archived row for export and 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 project inside a password-protected portal page so clients see the upvote board without needing an Asana seat at all.

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