Skip to main content

Permissions and Governance

Summary​

Organization administration is tenant-scoped and authenticated. HR designations describe workforce placement; security roles and permissions determine application access. Neither should implicitly create the other.

Audience​

  • Platform and tenant administrators
  • Implementation, support, engineering, architecture, security, and product teams

Purpose​

These principles provide public-safe governance for organization master data without disclosing exact policies, internal trust paths, or development behavior.

Architecture​

Business concepts​

  • Tenant-scoped administration: organization reads and changes operate in tenant context; platform-wide administration is a separate authority.
  • Role-based administration: protected services and monolith compatibility controllers require authenticated administrative access. Exact policy names are intentionally omitted.
  • Designation versus security role: designation is Employee Service workforce master data; roles and permissions belong to Identity/application authorization.
  • Auditability: department/designation operations and employee assignment changes create audit records; employee changes can also create timeline and outbox records.
  • Least privilege: company, organization-master, employee-assignment, and platform-wide operations should be granted independently.
  • Change review: parent/head changes, deactivation, reassignment, and role changes should have named owners and an approved review path.
  • Data quality: unique codes, active-reference checks, tenant consistency, designation/department compatibility, and manager self-reference checks support integrity.
  • Ownership boundaries: Platform owns company control-plane data; Employee Service owns workforce organization; Identity owns authorization data.

Technical implementation​

Employee Service uses tenant-aware repositories and query filters plus command validators. Platform and monolith endpoints apply their own authenticated administration boundaries. Because authorization implementation and cutover are transitional, this page states governance expectations rather than exact internal policy mechanics.

Hierarchy-cycle validation beyond direct self-reference, separation-of-duties policy, approval workflows, and formal data-steward roles Require confirmation.

Source References​

  • microservices/src/employee-service/Program.cs
  • microservices/src/employee-service/Application/Common/Abstractions.cs
  • microservices/src/employee-service/Application/Validators/EmployeeCommandValidators.cs
  • microservices/src/employee-service/Infrastructure/EmployeeDbContext.cs
  • microservices/src/employee-service/Infrastructure/Persistence.cs
  • microservices/src/platform-service/Api/PlatformAdminEndpoints.cs
  • Controllers/DepartmentsController.cs
  • Controllers/DesignationsController.cs
  • microservices/src/identity-service/Domain/Entities/Role.cs

See Also​

Keywords​

  • Organization governance
  • Tenant authorization
  • Master-data quality

Revision Information​

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