Skip to main content

Organization Overview

Summary​

Organization administration spans two service boundaries: Platform owns the tenant-linked company profile and platform settings, while Employee Service owns workforce departments, designations, employee assignments, and reporting-manager references.

Audience​

  • Platform and tenant administrators
  • Implementation partners
  • Developers, DevOps engineers, architects, security engineers, and product owners

Overview​

The organization model links a Platform tenant and client to company metadata, then uses the shared tenant identity to scope Employee Service organization masters and employee records. Identity supplies authenticated user and tenant context. Gateway routing selects Employee Service or monolith compatibility surfaces during cutover.

Purpose​

This boundary provides company identity and workforce structure without treating an HR designation as an Identity authorization role or assuming that every downstream service automatically receives organization changes.

Architecture​

Dashed relationships indicate transitional or integration boundaries whose complete production adoption is not confirmed by source alone.

Business concepts​

  • Tenant: common scope connecting Platform and Employee data.
  • Platform client: control-plane customer record linked to tenant-owned branding and commercial data.
  • Company: Platform-owned legal/display/contact/locale profile for a tenant.
  • Department: Employee-owned tenant-scoped organizational unit with optional parent and head references.
  • Designation: Employee-owned tenant-scoped job designation, optionally associated with a department.
  • Employee: workforce aggregate that can reference department, designation, and reporting manager.
  • Reporting hierarchy: employee-manager references in Employee Service and a transitional user-manager hierarchy in the monolith UI.

Technical implementation​

  • Implemented: Employee Service aggregates, validators, commands, queries, PostgreSQL persistence, audit records, timelines, and outbox mapping.
  • Transitional: compatible employee/department/designation contracts and Gateway feature-controlled ownership coexist with monolith controllers and UI routes.
  • Requires confirmation: final company-to-organization synchronization, production route ownership, and downstream handling of organization events.

Source References​

  • microservices/src/employee-service/Program.cs
  • microservices/src/employee-service/Domain/Organization/Organization.cs
  • microservices/src/employee-service/Domain/Employees/Employee.cs
  • microservices/src/employee-service/Infrastructure/EmployeeDbContext.cs
  • microservices/src/platform-service/Domain/Entities/Company.cs
  • microservices/src/platform-service/Domain/Entities/CompanySetting.cs
  • microservices/src/gateway-api/Program.cs
  • Controllers/DepartmentsController.cs
  • Controllers/DesignationsController.cs

See Also​

Keywords​

  • Organization boundary
  • Workforce master data
  • Transitional cutover

Revision Information​

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