Integrations and source ownership

• Learning platform. Course content and online submissions stay in your learning platform; enrollments and published sessions can be shared with it.

• Payment provider. Fee payments are taken by your payment provider, and paid amounts are recorded against each fee.

• Room booking system. If rooms are also booked for meetings elsewhere, those bookings can be recorded as unavailable intervals.

• Identity provider. Map staff and instructors to user accounts; disabling a sign-in must remove access here too.

Each connection needs an agreed source of truth, field mapping, event identifier and retry policy. Keep credentials in the approved secret store and grant the smallest permitted scope. A repeated payment event must not record a payment twice, and a repeated enrollment must not take a second place. Queue rejected records with their source identifier and a visible reason.

Reconcile source totals to accepted, rejected and pending events. Review a provider timeout, a duplicate delivery, a changed source record and a revoked credential before enabling schedules. Availability depends on each provider’s API, commercial access and configuration.

Use the implementation plan to agree integration acceptance criteria.