No. SleekView reads from the same job_application post type and meta fields WP Job Manager Applications already writes. Votes and notes append as new meta and post records, so the original plugin keeps working unchanged, and a SleekView uninstall leaves every candidate record intact in the database.

Yes. Each user gets one vote per card, and the board surfaces the combined count as the primary rank, with manager votes weighted higher if you choose. You can also split votes by role into separate columns so the sync meeting sees recruiter score, manager score, and weighted total at a glance.

Set the board visibility to a specific WordPress role or to logged-in only with capability checks. Anonymous voting is disabled by default for application boards, and the public preview link can be revoked at any time. You can also IP-restrict the board to office or VPN traffic for stricter security.

Optionally. SleekView fires the same WP Job Manager Applications status change hooks, so any existing notification templates for moved-to-interview or moved-to-rejected continue to run. You can suppress notifications per status if your team prefers to send manual rejection emails with personalized feedback.

Yes. The board exports as CSV, JSON, or printable PDF from the admin toolbar. The export carries vote count, status, category, recruiter notes, and timestamp, so an offsite interview panel can read every candidate score and reasoning without logging into the WordPress admin or needing access to the plugin.

Yes. Each board filters by job listing, so an engineering recruiter only sees engineering applications and only votes there. The combined vote count for a candidate only includes votes from people who actually reviewed that role, so cross-role bias never leaks into the scoring of unrelated positions.

Each application stays a separate card by default because each role has its own scorecard. You can also merge cards by candidate email, in which case the votes aggregate across roles and the status pills show the furthest-along stage. Both modes coexist, so the team picks the right view per role.

Votes and notes remain in the database attached to each application, so future hiring rounds can reference the prior pipeline. The board archives closed jobs into a separate view, so the active pipeline stays clean, and a permanent searchable archive supports compliance and audit requirements over the long term.