Summary
KC Safety integrates with the KnowledgeCity Learning Platform so that safety training is assigned and tracked in one place. When a training rule or a manual assignment calls for it, KC Safety pushes the enrollment to the KC LMS, and course and learner data is mirrored back into KC Safety. The connection is enabled per account under Settings → Integrations → LMS Integration.
Introduction
Safety work and safety training are closely linked. An incident may call for retraining, a role may require a certification to stay current, and a compliance review usually needs evidence that the right people completed the right courses.
Keeping those two systems aligned by hand does not scale: someone has to enroll learners in the LMS, then copy completion records back into the safety record. The LMS integration removes that manual step. Training that KC Safety decides is needed becomes an enrollment in the KC LMS automatically, and the resulting course and learner data is reflected back so KC Safety can report on it.
You will need the Super Admin role to enable and configure the connection.
Key Concepts
- Training rule — a rule in KC Safety that determines training is required, which then produces an enrollment.
- Manual assignment — training assigned directly to a person in KC Safety, rather than by a rule.
- Enrollment push — KC Safety sending an enrollment to the KC LMS so the learner is registered on the course.
- Mirrored course and learner data — course and learner information brought back from the LMS into KC Safety, so training status is visible alongside safety records.
- Outbound OAuth2 connection — the authorization model for the link: KC Safety authenticates to the KC LMS and calls it.
Steps to Follow
Understanding the direction of the connection
This integration is outbound from KC Safety's point of view. KC Safety authenticates to the KC LMS using OAuth2 and calls the LMS to push enrollments and read course and learner data back.
There is no inbound webhook from the LMS to KC Safety. Everything flows through calls that KC Safety initiates, which means updates appear in KC Safety when KC Safety next requests them rather than being pushed the instant they happen in the LMS.
Locating the LMS Integration settings
Sign in as a Super Admin and go to Admin Panel → Settings → Integrations → LMS Integration. The connection is configured per account, so it affects only your own KC Safety account.
Knowing what the integration moves
Once the connection is active:
- Training enrollments generated by training rules are pushed to the KC LMS.
- Training assigned through a manual assignment in KC Safety is pushed the same way.
- Course and learner data from the LMS is mirrored back into KC Safety, so training status can be seen and reported on next to the safety records it relates to.
Getting help with setup and troubleshooting
Because this integration has its own setup steps, data flows, and failure modes, the detailed configuration and troubleshooting procedure is maintained separately. Contact your KnowledgeCity representative or KnowledgeCity Support for the LMS integration setup guide, and use it for anything LMS-specific — connection setup, mapping, and diagnosing enrollments that do not appear.
Conclusion
The LMS integration connects safety training decisions in KC Safety to delivery and record-keeping in the KC Learning Platform. Enrollments from training rules and manual assignments are pushed to the LMS over an outbound OAuth2 connection, and course and learner data is mirrored back so training status is visible where the safety work is. Enable it per account under Settings → Integrations → LMS Integration, and use the dedicated LMS integration guide for detailed setup and troubleshooting.