From 137801d6f1943eedf675ab449c17bcf9a9685fa2 Mon Sep 17 00:00:00 2001 From: Joseph Spiker Date: Tue, 6 Oct 2026 04:16:36 -0400 Subject: [PATCH] docs: correct Hiring Page in the beta README Evidence: spikersoft-backend@master SpikerSoft.Api/Domain/Positions/PositionsController.cs:63 an ambassador row is built for every active location. Co-authored-by: Cursor --- README.md | 21 ++++++++++----------- 1 file changed, 10 insertions(+), 11 deletions(-) diff --git a/README.md b/README.md index 9deba2e..3f19ebb 100644 --- a/README.md +++ b/README.md @@ -1689,24 +1689,23 @@ The `/employment` route is a **master-detail careers page** (it replaced a flat Position sources remain two-fold: -1. **Ambassador Positions** — Auto-generated for every active `Location` that does not have an assigned ambassador, so the page always reflects current staffing gaps. +1. **Ambassador Positions** — Generated for every active `Location`. A location that already has an ambassador is shown as filled; an unassigned location is an open opening. 2. **Other Roles** — Manually created positions (developer, designer, teacher, etc.) managed through the admin Location Management page. -- **Backend**: `PositionsController` (`GET /api/positions`) merges manually created `OpenPosition` documents with auto-generated ambassador entries for unassigned locations. +- **Backend**: `PositionsController` (`GET /api/positions`) merges manually created `OpenPosition` documents with an ambassador entry for every active location, filled or open. - **Frontend**: `EmploymentComponent` + `employment-filters` / `employment-list` / `employment-detail` children, backed by `PositionCatalogService`. ### Ambassador Application Workflow -Clicking an **open** position card launches a multi-step application dialog (`ApplicationDialogComponent`). Applicants must be logged in. +**Apply** on an open role in the detail pane launches a multi-step application dialog (`ApplicationDialogComponent`). Applicants must be logged in. **Intake Form Steps:** -1. **Position & Passport** — Read-only position summary, optional passport image scan via OCR (reuses the same `IPassportOcrService` / Tesseract OCR pipeline as the child account flow). -2. **Personal Information** — Name, DOB, sex, nationality, citizenship, government ID (SSN / National ID / Tax ID), email, phone. Fields auto-populate from passport scan results. -3. **Address History** — Current and previous addresses with date ranges. -4. **Work & Education** — Employment history and education entries. -5. **References** — Minimum 2 professional/personal references. -6. **Consent & Submit** — Background check authorization and terms acceptance. +1. **Applicant Profile** — Read-only position summary, optional passport image scan via OCR (reuses the same `IPassportOcrService` / Tesseract OCR pipeline as the child account flow), then name, DOB, sex, nationality, citizenship, government ID (SSN / National ID / Tax ID), email, and phone. Fields auto-populate from passport scan results. +2. **Address History** — Current and previous addresses with date ranges. +3. **Work & Education** — Employment history and education entries. +4. **References** — Minimum 2 professional/personal references. +5. **Review & Submit** — Background check authorization and terms acceptance. **Application Status Lifecycle:** @@ -1716,10 +1715,10 @@ Applications can be `Rejected` at any review stage with a reason. **Admin Review:** -Staff/Admin users access the review panel at `/admin/application-review` (menu item: "Applications" with pending count badge). From there they can: +Staff/Admin users access the review panel at `/admin/application-review` (menu item: "Hiring" with pending count badge). From there they can: - Begin review, initiate background checks (provider selected automatically by country), approve/reject, and hire. -- The **Hire** action creates a Keycloak account with the `Staff` role, creates a `PositionAssignment`, and marks the application as `Hired`. +- The **Hire** action promotes the applicant's existing Keycloak account when they have one, and creates an account only when they do not. A guide application enrolls them as a guide. Any other hire assigns the `staff` realm role, creates a `PositionAssignment`, and marks the application as `Hired`. | File | Purpose | |------|---------|