Integrations and source ownership

• Student information system. Learner records and numbers come from your SIS; enrollments can be shared back.

• Payment provider. Activity fees are paid through your payment provider and paid amounts are recorded here.

• League and meet systems. Fixtures and results stay in your league system; placings become achievements with the official sheet.

• Identity provider. Map staff and coaches 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.