Talent & Acquisition Hub
Recruitment, CV screening, skills and performance across your talent pipeline in one consolidated screen.
Overview
Talent & Acquisition Hub consolidates the talent lifecycle screens — recruitment, AI-assisted CV screening, employee skills and performance tracking — into a single page with an internal sub-navigation list. Selecting an item on the left renders that sub-screen’s content inline in the same page, without a full navigation away from the hub. It is one of the three hubs shown in the sidebar when Hub view mode is active for the Human Resources module, covering everything from sourcing candidates through evaluating current employees’ skills and performance.
Talent & Acquisition Hub does not introduce any new talent-management logic of its own — all four sub-screens render the exact same components used by their standalone Grid View screens. All four are fully live; none are placeholders.
What's Included
| Sub-screen | Status | Description |
|---|---|---|
| Recruitment | Live | Job openings, candidate pipelines and hiring stages, reused from the standalone Recruitment screen. |
| CV Screening | Live | AI-assisted resume screening against job requirements, reused from the standalone CV Screening screen. |
| Skills | Live | Employee Skills — a skills inventory across the workforce, reused from the standalone Employee Skills screen. |
| Performance | Live | Performance KPI — performance review and KPI tracking, reused from the standalone Performance KPI screen. |
AI Assistant
Talent & Acquisition Hub includes a single, hub-level built-in AI Assistant, opened from the collapsed AI Assistant tab anchored to the right edge of the screen (click it to slide the panel open; click the tab on the panel's own left edge, or its header X, to close it again). Its context follows whichever sub-screen you currently have selected on the left — Recruitment, CV Screening, Skills or Performance — and updates automatically the moment you switch tabs, without needing to reopen the panel. Example questions it can answer:
- A summary of what's currently visible on the active sub-screen
- Coverage gaps or missing data on that sub-screen (for example, candidates stuck in one pipeline stage, or employees with no recorded skills)
- Who stands out on the active sub-screen — top-rated candidates or top-performing employees
- Natural follow-up questions building on its previous answer
One assistant per hub, not one per sub-screen
Recruitment, CV Screening, Skills and Performance each ship with their own AI Assistant when opened standalone from Grid View (Recruitment, CV Screening, Employee Skills, Performance KPI). Inside this hub, all four sub-screens' own assistant panels are suppressed so you only ever see one AI Assistant entry point on screen at a time — the hub's own panel, scoped to whichever tab is active.
Replies can be saved as a report (Save as Report) for later reference, and you can attach existing Knowledge sources to ground its answers in additional context beyond the active sub-screen's data.
How It Works
All four sub-screens are fully live and reuse the exact same underlying components as their Grid View counterparts, so candidate and employee data entered in one view mode is immediately visible in the other. Candidates hired through Recruitment and screened through CV Screening become employee records that flow directly into Core HR & Organization Hub’s Employees list once hired, and their skills and performance are then tracked through the Skills and Performance sub-screens here.
CV Screening Is AI-Powered
Resume scoring runs through your configured writer engine
CV Screening does not use keyword matching — it sends each candidate’s resume, together with the job’s must-have criteria and weighted scoring categories (education, experience, technical skills, soft skills, language match), to an LLM prompt that returns a 0–100 score, a pass/fail verdict and a per-category breakdown with notes. Which model actually performs the scoring depends on your Settings → Agentic → Writer Engine selection: ollama, local-llm and web-llm run entirely client-side (or against your own local Ollama instance) so no resume content leaves the browser/machine, while api and local-cli route the scoring request through the server. CV Screening checks this setting before every scoring call, so switching engines in Settings takes effect immediately without any extra configuration in HR.
Must-have criteria act as hard gates: if a resume is clearly missing a must-have requirement, the score is capped low and the candidate is marked as failed regardless of how strong the other categories score. The threshold for what counts as a pass, and the category weights used to compute the overall score, are configurable per job opening.
Hub View vs. Grid View
TotalApp’s Human Resources module supports two view modes, controlled from Settings → Appearance or the sidebar view-mode toggle:
Sidebar shows 3 consolidated hub entries — Core HR & Organization, Talent & Acquisition, Time & Operations.
Sidebar shows individual entries instead — Recruitment, CV Screening, Employee Skills, Performance KPI, and so on.
Both view modes read and write the same underlying tenant data — switching between them changes only how screens are organized for navigation, never the data itself.
My Workspace self-service screens are unaffected
HR’s employee self-service screens (My Leaves, My Expenses, My Overtime, My Assets) live under My Workspace, not under the Human Resources sidebar group, and are not part of this Hub View vs. Grid View toggle at all — they are unrelated to Talent & Acquisition Hub’s content and stay visible the same way regardless of which HR view mode is active. See Time & Operations Hub for the manager-facing approval screens that are affected by this toggle.
Frequently Asked Questions
writerEngine setting before every scoring request. When ollama, local-llm or web-llm is selected, scoring runs entirely client-side or against your local Ollama instance; only api and local-cli route the request to the server.CVScreeningScreen) rendered inline inside the hub, not a copy. Candidates screened in one view mode are immediately visible in the other.