Skip to main content

Organization and Company Administration

Summary​

This section documents the source-confirmed company and organization model across Platform, Employee Service, Gateway, and transitional monolith/UI surfaces. It distinguishes company profile ownership from workforce organization ownership and labels incomplete integration explicitly.

Audience​

  • Platform and tenant administrators
  • Implementation and support teams
  • Developers, architects, security engineers, and product owners

Overview​

Start with Organization overview for responsibilities, ownership boundaries, and maturity.

Business Documentation​

Business documentation covers company structure, departments, designations, hierarchy, lifecycle, and employee assignments.

Technical Documentation​

Technical documentation provides the implementation and service-boundary entry point.

API Documentation​

API documentation is the stable entry point for approved endpoint reference.

Database Documentation​

Database documentation covers data ownership, persistence, and tenant isolation.

Events​

Events covers organization-related employee events and integrations.

UI​

UI documentation groups approved organization administration and hierarchy interface guidance.

Operations​

Operations covers administration, permissions, governance, and safe operations.

Reference​

Reference provides stable organization master-data reference.

Troubleshooting​

Troubleshooting provides safe diagnosis and resolution guidance.

Purpose​

The section provides public-safe architectural and administrative guidance without exposing internal route tables, environment configuration, personal data, or sensitive operating procedures.

Current maturity​

  • Implemented: tenant-scoped department and designation masters, employee department/designation/manager references, validation, search, audit, timelines, and outbox event creation exist in Employee Service.
  • Transitional: Gateway-controlled cutover, compatibility contracts, monolith organization administration, user-based organization charts, and duplicate company-settings models coexist.
  • Foundation: employee integration events and service-owned PostgreSQL persistence provide an extraction foundation.
  • Requires confirmation: production cutover state, event consumers for organization changes, multi-company policy, complete hierarchy governance, and downstream synchronization.

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/platform-service/Domain/Entities/Company.cs
  • microservices/src/gateway-api/Program.cs

See Also​

Keywords​

  • Organization ownership
  • Company administration
  • Workforce structure

Revision Information​

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