Company Structure
Summary
Platform stores tenant-linked company identity and settings. Employee Service uses the tenant scope—not a separate company aggregate—to own departments, designations, and employees.
Audience
- Platform and tenant administrators
- Implementation partners, developers, architects, and product owners
Purpose
Use this model to keep control-plane company metadata separate from workforce organization masters while preserving their tenant relationship.
Architecture
The hierarchy is conceptual and does not assert a multi-company, legal-entity, branch, or location hierarchy.
Business concepts
- Company — Implemented: Platform models legal name, display name, contact, address, regional, and locale metadata owned by a tenant.
- Tenant ownership — Implemented: company records and company settings carry the Platform tenant reference; Employee Service organization data carries the shared tenant identity.
- Company settings — Implemented / Transitional: Platform has tenant-scoped category/key/value settings, while the monolith retains a separate typed company-settings model.
- Branding — Implemented: branding is associated with the platform client and resolved in the tenant context; it is distinct from the company profile.
- Company-level configuration — Foundation: Platform supports tenant-scoped configuration and secret references; operational ownership requires confirmation.
- Departments and employees — Implemented: Employee Service owns these within tenant scope, not as children of a local Company entity.
- Multi-company behavior — Requires confirmation: reviewed source does not establish approved multi-company or multiple-legal-entity behavior within one tenant.
- Branches and location hierarchy — Requires confirmation: department and employment records contain optional location text, but no governed branch/location hierarchy was confirmed.
Technical implementation
Platform administration retrieves and updates company profiles and settings. Employee Service applies tenant query filters to departments, designations, employees, audits, and employee child data. No reviewed event or application service automatically copies Platform Company details into Employee Service.
Source References
microservices/src/platform-service/Domain/Entities/Company.csmicroservices/src/platform-service/Domain/Entities/CompanySetting.csmicroservices/src/platform-service/Domain/Entities/TenantBranding.csmicroservices/src/platform-service/Api/PlatformAdminEndpoints.csmicroservices/src/platform-service/Data/PlatformDbContext.csmicroservices/src/employee-service/Infrastructure/EmployeeDbContext.csControllers/CompanySettingsController.csModels/CompanySetting.cs
Related Articles
See Also
Keywords
- Company identity
- Tenant settings
- Workforce structure
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly