LMS Business Integrations

Summary

Confirmed integrations are limited to implemented boundaries.

Boundary	Confirmed behavior
Gateway	Employee self-service proxy/aggregation and portal routing
Identity	Tenant/user request context; fine-grained service policy incomplete
Employee	References and ESS presentation; no direct Employee Service client
Document	Material storage/download and certificate document generation/download
Notification	Recognizes nine Training contract types
Messaging	Transactional outbox intent and shared contracts
Workflow	No Training Workflow integration found
Platform, Payroll, Performance	No direct LMS business integration found

Requires confirmation

Business ownership, policy approval, fine-grained eligibility, service objectives, and future lifecycle governance require confirmation where not implemented.

Source References

• microservices/src/training-service/Program.cs
• microservices/src/training-service/Application/DocumentServiceClient.cs
• microservices/src/contracts/Events/TrainingLifecycleEvents.cs
• microservices/src/notification-service/Application/EventNotificationResolver.cs
• microservices/src/gateway-api/EssEndpoints.cs

Related Articles

• LMS business documentation
• LMS overview

See Also

• Known limitations
• Integrations

Keywords

• Learning Management System
• Training business behavior

Revision Information

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