Skip to main content

Employee Organization Integration

Summary​

Organization behavior is not a separate executable service in the reviewed source. Employee Service owns Department, Designation, employee organization references, and reporting-manager relationships; Platform separately owns tenant-linked company/control-plane data.

Audience​

  • Backend developers and QA engineers
  • Solution architects and product owners

Purpose​

Explain the internal Employee/Organization relationship and the separate Platform boundary.

Confirmed integration​

  • Employee, Department, and Designation are modeled in the same bounded-context project.
  • Employee holds optional current references to Department, Designation, and another Employee as reporting manager.
  • Application validators and services enforce active reference and uniqueness rules where implemented.
  • Department and manager changes use Employee aggregate behavior, audit, timeline, and outbox foundations.
  • Department and Designation use application services plus repository/unit-of-work ports.
  • Tenant identity connects Employee-owned workforce organization data with Platform-owned company data.
  • No direct Employee-to-Platform HTTP client or automatic company-data copy is registered.

The Organization documentation already covers business behavior. Database schema and event payloads remain outside this epic.

Requires confirmation​

  • Final company-to-workforce synchronization.
  • Cross-service organization master ownership after migration.
  • Complete hierarchy cycle enforcement.
  • Production ownership of the existing user-based organization chart.

Source References​

  • microservices/src/employee-service/Domain/Employees/Employee.cs
  • microservices/src/employee-service/Domain/Organization/Organization.cs
  • microservices/src/employee-service/Application/Organization/Organization.cs
  • microservices/src/employee-service/Application/Validators/EmployeeCommandValidators.cs
  • microservices/src/platform-service/Domain/Entities/Company.cs

See Also​

Keywords​

  • Workforce organization
  • Internal bounded-context integration
  • Company boundary

Revision Information​

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