LMS Employee Integration

Summary

Training stores numeric employee/user references and optional email on enrollments, completions, attempts, and certificates. No Employee Service HTTP client, repository, or event consumer exists.

Gateway ESS calls the Training enrollment list and composes it into employee self-service; the React page renders a read-only Training list. Administrative UI accepts employee references directly. The manager report route currently scopes its identifier directly to employee data rather than resolving a reporting hierarchy.

Employee profile/data ownership stays outside Training. Eligibility, employment-status validation, manager hierarchy, self-only API filtering, synchronization, deletion/retention, and reassignment behavior require confirmation. Personal records are intentionally excluded.

Requires confirmation

Fine-grained authorization, production ownership, operational governance, and future architectural boundaries require confirmation where not implemented.

Source References

• microservices/src/training-service/Domain/TrainingEntities.cs
• microservices/src/training-service/Api/TrainingEndpoints.cs
• microservices/src/gateway-api/EssEndpoints.cs
• UI/salary-ui/apps/client-hrms-portal/src/ess/EssPages.tsx

Related Articles

• LMS technical documentation
• LMS business documentation

See Also

• Technical limitations
• Technical source map

Keywords

• LMS technical architecture
• Source-backed implementation

Revision Information

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