Use Cases
Sell a Course
Publish a course, list it in Academy, connect payments, and share a product link.
Situation
You want people outside your usual assignees to discover, request, or buy a course through Academy—the storefront—then take it in Learn.
Outcome
A published course is an Academy product. Learners enroll via product link and/or the Academy catalog; paid orders complete in Academy and the course shows up in Learn (subject to visibility and any licenses).
Who
Administrators (catalog and payments via Manage Academy) and content creators (publish and enable Academy Visibility in Create).
Path
- Build and publish the course in Create.
- Connect payments (for paid sales) under Supported Payment Options—Activate Commerce, then Stripe integration or Manual flow.
- Enable Academy Visibility on the course (in Create, or under Manage Academy → Content). Choose availability: Purchase, Public, Available / Users, or Approval. Details: Academy Catalog Visibility vs Product Availability.
- Decide who can open the Academy catalog under Manage Academy → Visibility (same guide as above)—independent of how each product is offered.
- Share the product link via Share Link (Academy destination) or copy it from product settings. Keep the workspace Academy admin-only if you only want link-based access—see Public Content.
- Optionally organize the catalog with Collections.
Tips
- Public product links can let anonymous learners start without an account; signed-in flows still use Learn as usual.
- Approval is manager-approved free access—not a payment method. Configure it on the product, not under Payment.
- Catalog visibility (Manage Academy → Visibility) and per-product availability are separate dials—mixing them up is the usual setup mistake.
- For time-bounded paid access after purchase, use Sell With Content Licenses.
- When learners hit access dialogs in Learn, the button is Buy License—it opens the Academy product even when the issue is visibility. See Visibility in Learn.
