Skip to main content

Organization Assignment Storage

Audience​

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

Reference Content​

Summary​

Department, designation, manager and work-location assignments are represented differently across the extracted Employee model and the compatibility workforce model.

Extracted Employee boundary​

Employee stores department, designation and manager references plus work-location data in its aggregate/employment value. Department and Designation are separately persisted Employee-context roots with tenant/code uniqueness. The mapping does not configure database foreign keys from Employee to those roots or to a manager Employee.

Assignment flow​

Integrity implications​

  • Organization references can be syntactically present without database-enforced existence.
  • Cross-context organization data cannot be protected by relational foreign keys.
  • Deletion and reassignment behavior are application concerns.
  • The compatibility workforce model is separate from Employee Service organization assignment.

Open assignment questions​

Canonical organization ownership, reference validation at write time, stale-reference handling and historical assignment tracking require confirmation.

Requires confirmation​

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

Source References​

  • microservices/src/employee-service/Infrastructure/EmployeeDbContext.cs
  • microservices/src/employee-service/Domain/Employees/Employee.cs

See Also​

Keywords​

  • Onboarding database
  • Offboarding database
  • Lifecycle persistence

Revision Information​

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