LOB configs
LOB configs are how an assessment template gets in front of candidates. A LOB config binds a template to:
- A client account + LOB
- A pipeline stage (Stage 1 = inline at apply, Stage 2 = email-invite later)
- Delivery and gating rules
/recruiting/assessments/lob-configs
Layout
An account dropdown filters the visible LOBs. The table has one row per LOB with two stage cells (Stage 1 and Stage 2). Each cell is either:
- Not configured — with a Configure button, or
- Configured — with badges summarising the binding
Configured-cell badges show:
| Badge | Meaning |
|---|---|
| Engine | Native (FrontLine assessment engine) or third-party |
| Delivery mode | Synchronous (inline) or email-invite |
| Gate | Pass-through, soft-gate (warn), hard-gate (block on fail) |
| Auto-advance | Stage 1 only — auto-progress on pass to skip manual review |
Configuring a stage
The edit dialog (LobConfigDialog) sets:
- Template (only active templates of the matching language are listed)
- Time restrictions (e.g., complete-within window, lockout period after fail)
- Pass / fail thresholds for the stage
Stage 1 vs. Stage 2
| Stage 1 | Stage 2 | |
|---|---|---|
| Trigger | Candidate applies | Recruiter advances candidate |
| Delivery | Inline (synchronous) typically | Email-invite typically |
| Use case | Quick screen — typing test, basic SJT | Full-length — deep cognitive / role-specific |
| Auto-advance | Optional | N/A |
Why this matters
Without a LOB config, no candidate is ever asked to take an assessment for that LOB and stage — even if a template exists. LOB configs are the active binding that makes the engine actually run.