Recruitment Onboarding Storage
Summary
Onboarding persists handoff state and logical Candidate, Offer, Employee, user, and manager references.
Audience
Developers, QA and support engineers, data reviewers, implementation partners, solution architects, and security reviewers.
Overview
Onboarding is an aggregate root with a primary key, unique compatibility identity, tenant/status index, and tenant/candidate/offer composite index.
CandidateId, OfferId, created Employee identifiers, user identifier, and reporting-manager identifier are logical references without EF relationships. The model therefore does not database-enforce that those referenced records exist.
Employee provisioning occurs externally before the Recruitment completion save. There is no distributed transaction or persisted reconciliation queue for that boundary.
Requires confirmation
Production migration governance, rollback ownership, reconciliation, retention, privacy, performance, query optimization, concurrency, and operational ownership require confirmation.
Source References
microservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.csmicroservices/src/recruitment-service/Domain/Recruitment/Onboarding.csmicroservices/src/recruitment-service/Infrastructure/EmployeeServiceClient.cs
Related Articles
See Also
Keywords
- Recruitment database
- Onboarding Storage
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly