Skip to main content

Recruitment Onboarding Storage

Audience​

Developers, QA and support engineers, data reviewers, implementation partners, solution architects, privacy reviewers and security reviewers.

Reference Content​

Summary​

The extracted Recruitment onboarding aggregate stores the accepted-offer transition, intended joining data, lifecycle status, employee linkage produced at completion and local evidence.

Logical model​

The candidate-to-offer and offer-to-onboarding links are stored identifiers but are not configured EF navigation relationships in the onboarding mapping. Child histories on Candidate and Offer do have configured relationships.

Stored responsibilities​

  • Candidate and offer references, joining date, status, notes and placement-related references.
  • Employee and user linkage after successful employee initialization.
  • Completion time and login-pending state.
  • Compatibility identifier used by compatibility-facing contracts.
  • Audit, timeline and outbox evidence saved with local completion changes.

Status behavior​

Creation begins in a pending/in-progress lifecycle. Completion marks onboarding complete and the candidate joined only after Employee Service returns success. Cancellation remains a local Recruitment state.

Integrity boundary​

A repository lookup for an active onboarding by offer bypasses global filters and does not add an explicit tenant predicate. This is a source-confirmed tenant-isolation concern and should be remediated or explicitly justified before production assurance.

Requires confirmation​

Unless explicitly confirmed above, production migration governance, rollback, reconciliation, retention, privacy, performance, concurrency and operational ownership require confirmation.

Source References​

  • microservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.cs
  • microservices/src/employee-service/Infrastructure/EmployeeDbContext.cs
  • Data/AppDbContext.cs

See Also​

Keywords​

  • Onboarding database
  • Offboarding database
  • Lifecycle persistence

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-20
  • Review cycle: Quarterly