Contact details as a paid gate
Most themes let you decide how a page looks. Superio's vendor feature list spends its longest section on who is allowed to see it. Under "Restrict Candidate," the option for viewing candidate contact info includes: all users and guests, all registered users, only applicants, registered employers, or — the line worth reading twice — everyone can view the candidate page, but only employers who bought a Contact Package can see the contact details.
That last setting defines a business model rather than a styling choice. Candidates stay visible and searchable, which keeps the board useful to visitors, while the email address or phone number that turns a profile into a hire stays behind a purchase. If your plan is to sell recruiter access rather than charge for job posts, this single dropdown is the feature to test first.
The same section separates the candidate page from the contact block, so you can open one and close the other: a public profile page with gated contact information sits between a fully open directory and a members-only one.
Gating jobs and employer profiles
"Restrict Job" controls the job page with four states: all users and guests, all registered users, registered candidates only, or always hidden. "Always hidden" is worth noting for a staged launch — listings can exist in the system without being publicly reachable.
On the employer side, the vendor lists a view setting for employer pages (all, registered users, only applicants, registered candidates, always hidden) with a parallel set of options for employer contact info.
These restrictions matter most alongside front-end job submission, which the vendor lists as a feature: an employer creates a listing from the site rather than through the WordPress admin. Once submissions arrive from outside the dashboard, the question of who can see what becomes a moderation decision you configure in advance, not something you patch later.
How the restriction options interact with each other — for example, whether a hidden job still counts toward an employer's listing total — isn't stated in the description. Plan to verify that in the demo or on a staging install before you publish a pricing page that promises a number.
Where listings come from: Fields Manager and four job feeds
Two features govern the sourcing side. The first is a Fields Manager, which the vendor lists first among the theme's features. Job boards live or die on the fields a listing carries — salary, contract type, location, experience — and the changelog mentions custom fields, required custom fields and filterable custom date fields across several releases, which suggests the manager is meant to be the control point for that structure.
The second is import. The vendor lists Indeed, CareerBuilder, Careerjet and ZipRecruiter job imports. Those four names describe the intended sources; the description doesn't say how an import is scheduled, how often it re-runs, whether imported listings are deduplicated, or how an imported record maps onto your custom fields. Those are the operational questions an aggregating board has to answer, and the listing doesn't answer them.
If you plan to run a board that is mostly syndicated listings, treat the import tools as the part that needs the most scrutiny. If you plan to accept employer submissions only, the Fields Manager carries more of the weight and the imports are a bonus.
Resumes, search and shortlisting
The vendor lists a Resume List shortcode and a Resume Advanced Search shortcode, alongside Listing List, Listing Search, Listing Advanced Search and Listing Simple Search shortcodes for jobs. Practically, that means job and candidate collections each get more than one presentation — a browsable list plus a filtered search view — and you choose which to place on a page.
The feature list also claims powerful sorting options for both job listings and resumes and multiple ways of showcasing each. Combined with the restriction settings above, the picture is a candidate directory with layered visibility: a visitor browses, a registered employer searches, and a package-holding employer sees contact details.
The changelog adds context the description leaves out: version 1.3.27 updated the resume builder, 1.2.35 touched Download CV and filtering, and 1.2.40 added social sharing for candidate profiles. Those are release notes from the vendor, not signs that a particular resume-building workflow is complete for your use case. Candidate résumés and personal data are also where privacy obligations land hardest, so decide early what a non-paying visitor is allowed to retrieve.
Maps, meetings and package tables
Job listings often hinge on location, and Superio declares three map providers: Google Maps, Here and Mapbox. Having alternatives is useful when one provider's key, quota or regional coverage is a problem, though the description doesn't say whether listings can mix providers or whether the choice is site-wide.
The feature list also names Meeting Zoom, and the changelog references meeting forms, scheduled meetings and Zoom email variables. Read together, that points to interview scheduling as a theme-level feature rather than a plugin you add. It is a vendor claim; the description doesn't explain what a meeting record contains or what happens on cancellation.
For monetisation, the vendor lists Pricing Tables and Comparison Pricing Tables shortcodes, which suit a page that lays out job-posting or CV-access packages side by side. With WooCommerce declared among the compatible plugins, checkout for those packages is a separate configuration job rather than a theme setting.
What the declarations do and do not tell you
Marketplace attributes observed on 3 November 2026 list Elementor and Elementor Pro, WooCommerce 6.x through 10.x, WPML, and WordPress 6.2.x through 7.0.x, with Gutenberg Optimized marked "Yes" and the package containing PHP, HTML, CSS, Sass and JS files. Those are listing declarations; they are not the result of installing or running the theme on a site.
The changelog is unusually long, and a few entries are relevant before you commit: versions 1.3.24 and 1.3.33 record vulnerability fixes, 1.3.31 a security update, and 1.3.23 a change to user registration. A job board collects personal data from both candidates and employers, so knowing that security patches have shipped is useful — but the changelog lines are one sentence each and say nothing about severity. If your install matters, run the current release and keep it updated rather than relying on a single older copy.
Superio's strongest claim is the permission matrix, not the page builder. Judge it by configuring a test board: one public listing, one hidden listing, one candidate visible without contact details. That exercise tells you more than any feature list about whether the theme matches how you intend to charge.
Questions & answers
Can I let anyone view a candidate profile but charge employers for their contact details?
The vendor lists exactly that option under the candidate restriction settings: profiles visible to all users, with contact information limited to employers who purchased a contact package. It's a description of an available setting, so confirm the purchase flow in the demo before building a pricing page around it.
Which job feeds can Superio import from?
The vendor names Indeed, CareerBuilder, Careerjet and ZipRecruiter. The description does not document import scheduling, deduplication or how imported fields map to your custom fields, so those details need checking against the theme's documentation.
Is candidate and employer data covered by any security updates?
The vendor changelog records vulnerability fixes in versions 1.3.24 and 1.3.33 and a security update in 1.3.31, without detail about severity or scope. That is a release-notes claim, not an audit result.