Patterns
Configure integrations
Connect a service, then select the course-specific destination.
On this page
Task sequence
- Inspect the provider’s connection card in Connections.
- Complete the provider’s own authorization outside the documentation fixture.
- Choose a Kit tag for enrolled students or a Stripe product for a paid course.
- Save the course setting and verify the selected destination.
Data and persistence boundary
Provider connection state and course configuration are different records. Kit tags and Stripe products are fetched into their settings pages; examples use fictional options.
Failure and recovery
A connected-looking card cannot establish token validity. Empty provider lists, expired authorization, and failed saves require production integration checks beyond these screenshots.
Source references
| File | Responsibility |
|---|---|
| src/app/dashboard/connections/page.tsx | Connection entry points |
| src/app/make-class/[classId]/email/page.tsx | Kit selection |
| src/app/make-class/[classId]/payments/page.tsx | Stripe selection |
Interface examples
Native TeachKit interfaces with fictional course, account, and learner records. Service responses and media are isolated demonstrations; no customer data or live changes. Captured at 2× resolution or higher. Select an image to inspect it full size.
Related topics
Source audit: 2026-10-22 · Revision 903bbf05ca9d · Documentation v2.0.0