Loading
Module
Post jobs to a public, SEO-friendly careers board on your own branded page — and on your own custom domain. Candidates apply directly with a lightweight account. Track applications, keep a talent pool, and give recruiters access scoped per job.
What this solves
A job posted on a third-party board is a rental. The traffic belongs to the board, the search ranking belongs to the board, and the candidate’s first impression of your company is a listing that looks like every other listing on that page.
A careers page on your own domain is an asset. It accumulates search ranking that stays yours. It looks like your company, because it carries your brand color. And a candidate who lands on it is already on your site rather than one click away from a competitor’s posting.
OneclickHR gives you that page, generated from the jobs you post, served on a custom domain you point at it, and built to be indexed.
What is included
Posted jobs become a public careers board built to be crawled and indexed, so a search for the role can find your posting.
The board carries your brand color, and you can point your own custom domain at it from workspace settings.
A candidate applies through the board with their own lightweight external account — no organization seat, no access to anything but their own application.
Applications are tracked against the job they came in on, so the state of a pipeline is a screen rather than an inbox.
Keep good candidates who were not right for one role, so the next opening starts with people you have already met.
Recruiters get access to the hiring side only, and that access is toggleable per job. A recruiter working one role does not see the rest of the organization.
For firms that place people on client engagements, placements are tracked as their own thing rather than inferred from a hire.
Employees see an internal job board in their own portal, so an opening can be filled from inside before it goes out.
Recruiting is where OneclickHR’s role model earns its keep. An organization admin configures everything. An employee sees the internal board. A recruiter sees the hiring side, for the specific jobs you toggled them onto. A candidate is external entirely — their own lightweight account, visibility of their own application, and nothing else.
Those boundaries are enforced by Row Level Security in the database, not by hiding buttons. A recruiter’s token carries their organization and role, and the database decides what rows they can read. Toggle a recruiter off a job and the access is gone on the next request, because access is re-checked from the database rather than trusted from an old token.
Recruiting shares its records with the rest of the workspace, so these modules read the same data rather than a copy of it.
Sign your organization up, configure your timezone and brand color, and invite your team. You can be running the same day.