A controlled system, not a collection of tools.
Role-based navigation, action-first dashboards and record-centric workspaces. Status, visibility and permissions always appear next to the primary action, so nothing is shared by accident.
Seven steps from brief to live card
- Step 1
Vacancy basics
Title, reference, role family, seniority, employment type and location create the draft record.
- Step 2
Link client
Select the client organisation, contacts and hiring manager. This sets the tenant boundary.
- Step 3
Build the card
Summary, responsibilities, requirements, benefits and process produce both previews.
- Step 4
Define criteria
Required and preferred taxonomies, skills and experience create match criteria and weights.
- Step 5
Configure application
Screening questions, required documents and the consent statement.
- Step 6
Select audience
Client visibility and candidate audience mode create explicit audience-grant records.
- Step 7
Review and publish
Preview as admin, client and candidate, validate required fields, then activate.
Everyone sees exactly what they should
| Portal | Primary users | Information boundary |
|---|---|---|
| Administrator | Recruiters, operations and agency administrators | Full authorised operational record, including the original CV and internal notes |
| Client | Client administrators, hiring managers and interviewers | Own organisation only; branded CV only; no internal recruitment notes |
| Candidate | Job seekers and registered talent | Own profile and applications; no internal scoring, rankings or client notes |
Canonical stages
- Applied
- Screening
- Shortlisted
- Submitted to client
- Interview
- Checks
- Offer
- Placed
Mandatory controls
- Server-side permission guards mirror every interface restriction.
- Consent is recorded with purpose, date granted, expiry and withdrawal.
- Every share, stage change and document version writes an audit event.
- Workspace records are strictly separated by workspace ID.