LMS Reference Documentation

Summary

Authoritative Draft catalogs cover terminology, statuses, permissions evidence, validation, integrations, maturity, limitations, and source ownership.

Audience

Business, product, engineering, QA, support, operations, architecture, security, and implementation teams.

Overview

Reference entries describe only verified implementation. A defined status does not prove a transition, a visible UI entry does not prove authorization, and a contract definition does not prove publication.

Documentation map

• Terminology, statuses, and validation
• Permissions and integrations
• Implementation status, limitations, and source map

Requires confirmation

Canonical business vocabulary ownership, permission policy, operational ownership, and future-state lifecycle governance require confirmation.

Source References

• microservices/src/training-service/Domain/TrainingEntities.cs
• microservices/src/training-service/Api/TrainingEndpoints.cs
• microservices/src/training-service/Application/Common.cs
• UI/salary-ui/apps/client-hrms-portal/src/components/AppLayout.tsx
• UI/salary-ui/apps/client-hrms-portal/src/utils/ProtectedRoute.tsx
• UI/salary-ui/apps/client-hrms-portal/src/dashboard/DashboardPages.tsx
• microservices/src/training-service/Program.cs
• microservices/src/training-service/Infrastructure/TrainingDbContext.cs
• microservices/src/gateway-api/EssEndpoints.cs
• microservices/src/training-service/Application/DocumentServiceClient.cs
• microservices/src/notification-service/Application/EventNotificationResolver.cs

Related Articles

• LMS module
• Business documentation
• Technical documentation

See Also

• API documentation
• UI documentation

Keywords

• LMS reference
• Verified catalogs

Revision Information

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