Run a SaaS customer academy with Learnomy

Pricing model: free training, or access tied to the product. Run an invite-only classroom, Phase 1, lists invite only, closed, free, and the five paid models. A product academy typically wants Free: any signed-in customer can self-enroll with no payment, since the training itself is not the product. Pick Closed instead when access should follow a paid tier or an account status inside your own app rather than being open to anyone who signs up -- for example, training reserved for customers on a specific plan.

Enrolling a customer from inside the app. For a Closed academy, the app needs a way to grant access the moment it decides a customer qualifies. Learnomy gives you two mechanisms, and they answer different questions:

Your options here:

• The incoming enrollment webhook -- your app POSTs a signed request to /wp-json/learnomy/v1/webhooks/enrollment with the buyer's email and course ID the moment an account becomes eligible (a plan upgrade, a new signup on a qualifying tier), and the same endpoint revokes access on "action": "revoke". Only closed courses are managed this way. Pick this for event-driven enrollment: your app already knows the moment eligibility changes, and the webhook reacts to that moment.
• The admin bulk-enroll REST route -- POST /learnomy/v1/admin/courses/{id}/bulk-enroll takes a batch of emails and enrolls (or invites) each one, admin-only. Pick this for a scheduled sync (a nightly job that reconciles your customer list against the training academy) rather than a real-time reaction to a single event.

A SaaS company wiring training into its own signup or upgrade flow usually wants the webhook: it is the one built to react to a single event as it happens. See Incoming Enrollment Webhook and Bulk Enroll from a List.

A certification badge worth sharing. Run a certification body, Phase 4, covers three credential forms that stack: PDF, Open Badges 3.0 (Pro), and a Credly push (Pro). A product academy's certification badge is usually Open Badges: once Certificates Pro is active it needs no setup beyond issuing the certificate, and it gives the customer a portable, machine-verifiable credential they can add to LinkedIn -- the natural way a customer shows off "Certified [Your Product] User." Add Credly on top only if your industry's employers already expect credentials to show up there; it is the one form of the three that needs you to connect an external account.

Keeping training off the public catalog. Run an invite-only classroom, Phase 2, covers per-course Visibility versus a site-wide Private site toggle. A SaaS company's main site is usually public marketing content, so the right choice is per-course Visibility: Private on the training courses only, not the site-wide toggle -- a logged-out visitor gets a plain not-found result for the training course while the rest of the site stays reachable.

Telling the rest of your stack when training happens. Two more integrations point the other direction from the enrollment webhook in item 2, notifying your CRM or backend instead of receiving from it:

Your options here:

• Outgoing webhooks -- at LMS Settings > Outgoing Webhooks, add a delivery URL and subscribe it to events such as course completion or certificate issued. Learnomy POSTs a signed JSON payload the moment the event fires, so your own backend or Zapier hears about it in real time. Free supports up to 3 webhooks; Pro's webhooks-pro extension removes the limit and adds 34 events with retry and HMAC signing.
• WP Fusion (Pro) -- if your CRM connects through WP Fusion, the bridge writes Learnomy tags back to the contact record as a customer enrolls, completes a course, or earns a certificate, and can also grant course access from a CRM tag the other way. It auto-enables once WP Fusion is active; there is no separate toggle.

A SaaS company usually wants both: the outgoing webhook for a real-time backend reaction, WP Fusion when the CRM itself should reflect training progress. See Outgoing Webhooks and WP Fusion.