by
Vakanssi
0 (0 reviews)
Vakanssi: Careers Page, Hiring & Applicant Tracking
A full applicant tracking system for WordPress: careers page, pipeline, interviews, hire. Self-hosted, with no per-seat fees.
Vakanssi ranks #60,080 among WordPress.org plugins with 0+ active installations, and was last updated Oct 29, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.4
v1.3.2
Current Version v1.3.2
Updated 1 week ago
Last Update on 29 Oct, 2026
Refreshed 1 week ago
Last Refreshed on
Downloads +375% this week
Actively maintained
Rank
#60,080
—
No change
Active Installs
0+
—
No change
KW Avg Position
35
0.2 better
Downloads
565
+154 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
32,512
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 8 more installs to reach 10+
Rank Changes
Current
#60,080
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.3.2
- Last Updated
- Oct 29, 2026
- Requires WP
- 6.6+
- Tested Up To
- 7.1.4
- PHP Version
- 7.4 or higher
- Author
- Vakanssi
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
Frequently Asked Questions
Common questions about Vakanssi: Careers Page, Hiring & Applicant Tracking
No. Uninstalling removes roles, capabilities, and plugin settings, but your hiring data is kept unless you explicitly enable Hiring → Settings → General → Delete all data on uninstall. While another copy of Vakanssi is still installed (for example in a second plugin folder), deleting a copy removes nothing, so the copy you keep runs with its settings and data.
Yes, with defence in depth. Candidate files are stored in a protected vakanssi folder in your uploads directory, under random 128-bit file names, with an Apache deny rule, index guards and a generated Nginx rule. Vakanssi then verifies over HTTP that the folder is not directly reachable, and shows an admin warning (with the exact Nginx rule to add) if it is. The plugin itself only serves CVs through an authenticated, permission-checked download link. To keep them outside your public site entirely, define VAKANSSI_STORAGE_DIR as an absolute path in wp-config.php; moving your existing CVs is covered at https://docs.vakanssi.com/admin/move-cv-storage/
Anyone you grant a hiring role to. Vakanssi ships three roles (Recruiter, Hiring Manager, and HR / Compliance) plus Administrator, and any user with the "view applications" capability can see every candidate and download every CV in the pipeline. In other words, Vakanssi does not restrict staff to only the jobs or candidates assigned to them: it assumes your hiring team is trusted, which is the right default for most small teams. Only grant these roles to people who should see all applicants.
Email security@vakanssi.com rather than posting in the support forum, so a fix can ship before the details are public. Please include the Vakanssi version, your WordPress and PHP versions, and steps to reproduce. You will get an acknowledgement within three business days and an initial assessment within a week, and you will be credited in the changelog for the release that fixes it unless you would rather not be. Only the most recent release receives security fixes, so updating
profile (name, email, phone, location), every application (position, stage, status, date, and whether consent was given), the cover letter, their LinkedIn profile, each uploaded CV/attachment (the file itself, with its filename and upload date), the submission context stored with the application (the page the application was sent from), the recruiter notes and interview notes written about them, their interviews, and the emails Vakanssi sent them. Other details stored with an application or the candidate are included too, under "Additional application data". The export deliberately does not name the staff member who wrote a note, gave a rating, or conducted an interview. That is a third party's personal data, not the candidate's. The matching Erase Personal Data tool removes all of it, including the CV files on disk. Export and erasure share one list of the tables that hold notes, interviews and emails about a candidate, so the two stay in step.
Yes, activated per site or network-wide. Each site keeps its own jobs, candidates, CVs and settings (data is never shared between sites), and each site chooses independently whether deleting the plugin also deletes its hiring data. There is no network-level configuration screen; settings are per site. Network activation is the recommended setup: deleting a site then removes that site's Vakanssi data with it, and if some of its CVs cannot be deleted, Vakanssi keeps the list of those files. With per-site activation, a site deleted where Vakanssi is not active keeps its Vakanssi tables, and its CVs when they are in a custom storage folder. Since 1.3.0 a super admin sees this data in Site Health and under Hiring → Tools → Data, and removes it there after a confirmation. When Vakanssi cannot prove a site's CV files are gone (for example a folder it cannot read), it keeps that site's file list and says why. A single site turned into a network keeps finding the CVs it stored before, and Site Health names the folder to move them from.
Yes. Nginx ignores .htaccess, so add the generated location block to your server config. The plugin's screens show the rule, and Site Health flags the folder, when it is reachable.
Yes, and you do not have to fall back to a shortcode. The block editor gets a Job Listings block. Elementor gets three native widgets (the listing, the application form, and the job details) grouped under a Vakanssi section in the panel, and they work with the free Elementor; if you run Elementor Pro, your Theme Builder archive and single templates for jobs are used instead of ours. Divi gets a Jobs module. Shortcodes ([vakanssi_jobs], [vakanssi_job_apply], [vakanssi_job_details]) still work anywhere else, including builders with no dedicated integration. Themes need nothing special. Block themes on WordPress 6.7 and later get editable "Jobs archive" (while the archive page is on) and "Single job" templates in the Site Editor, built from your own header and footer; classic themes get the built-in archive. The
apply button look the same whichever theme you run.
Yes. Under Hiring → Settings → Jobs & Careers → Appearance you can turn off Vakanssi's front-end stylesheet entirely, if your theme styles the markup. For your own styling, use WordPress's built-in editor at Appearance → Customize → Additional CSS, which adds no extra request. Vakanssi keeps its own selectors deliberately low-weight and its class names stable. Match their weight, such as .vakanssi-apply-form .vakanssi-apply-button for the application form's Submit button or .vakanssi-apply .vakanssi-apply-button for a job's Apply link, and style :hover, :focus and :active as well, since Vakanssi sets those too. On most pages that is enough without !important. The same vakanssi- class names are on the careers and job pages under block themes and classic themes alike, so one rule covers both. On a block theme your theme keeps control of the page width and spacing and Vakanssi adds no styling of its own to those wrappers, so your rules apply exactly as you write them.