White-label and tenant-branded
Your firm's brand, on your subdomain. The candidate experiences your agency, not a third-party tool.
Candidate Portal
Candidate data decays from the day it is captured. The Candidate Portal moves upkeep to the person who actually knows the answers — under your brand, and without exposing anything about your mandates or your other candidates. What the candidate submits does not overwrite your record: it arrives as a proposal a recruiter accepts or rejects, field by field.
The problem
A talent pool is only as good as its freshness, but keeping it fresh through recruiter effort alone does not scale — and the data most likely to be stale is exactly the data that matters most at submission time: availability, notice period, current role and whether the profile still describes the person accurately.
The portal is a distinct application from the recruiter workspace, with its own access model. Candidates see their own record and nothing else.
Your firm's brand, on your subdomain. The candidate experiences your agency, not a third-party tool.
Candidates are invited and sign in by secure link, which removes password friction and the support burden that comes with it.
Candidates keep their own contact details, availability, notice period and current situation current.
The candidate uploads a current CV straight into their own record, where it is read into structure the same way a recruiter upload is.
Candidate changes arrive as a proposal, not an edit. A recruiter reviews it and accepts or rejects each field on its own, so a well-meant correction can never quietly replace something you rely on.
An accepted profile update or an uploaded CV is written to the candidate's own history, so months later it is clear what changed, when, and that the candidate is the one who supplied it.
The portal exposes the candidate's own record only. Mandates, clients, other candidates and internal recruiter data are not reachable from it.
The interaction is short by design — the goal is current data, not engagement.
The recruiter invites the candidate from the candidate record.
The candidate signs in by link, without creating a password.
They confirm or correct their profile, availability and current role.
A recruiter sees the proposed changes and accepts or rejects each one.
Accepted updates flow back into the pool and into any active pairing.
An invite to a segment of the pool refreshes availability across hundreds of candidates without recruiter time per record.
Before a profile goes to a client, the candidate confirms their own details — and you approve what they changed.
A change to a candidate record carries the candidate's own action behind it rather than a recruiter's recollection of a call.
Upkeep moves to the person who knows the answer.
Candidates propose; recruiters decide. The pool never changes behind your back.
Candidates deal with your brand, not a generic form.
See it in motion
How the modules hand over to each other in the real product — customer and mandate, candidate and matrix, the workspace where a pairing is decided, and the material that goes to the client.
2 min
Continue across the platform
Structured CVs, skills, languages, eligibility and a reusable candidate matrix.
Learn morePermission groups, confidential mandates, enterprise sign-in and an append-only audit trail.
Learn moreBranded, invitation-only access for named client contacts — no shared logins, no attachments.
Learn moreA demo follows one mandate across every module, which is the only way the connections become obvious.