LearnWorlds setup guide: build the smallest complete school first

Prerequisites for LearnWorlds setup guide

Document the account owner, administrators, billing contact, domain owner, payment owner, support owner, and recovery method. Use individual access where supported and keep critical business assets under the company rather than an outside contractor. Decide how draft work is separated from the live school and how changes are approved.

Before design, record the intended plan and every capability the launch requires. This prevents a polished build from depending on a feature that is unavailable or unaffordable on the chosen tier.

• Assign named owners and backup access.
• Map requirements to the current plan.

Set up LearnWorlds setup guide step by step

Create the school navigation, one category or catalog path, one representative course, sections, lessons, resources, assessment, completion rule, and certificate when justified. Use consistent titles and descriptions that explain outcomes rather than internal file names. Configure prerequisite and drip behavior only when the teaching design needs it.

Complete the route as a learner before cloning templates. Early testing catches structural confusion before it is repeated across the catalog and makes later production faster.

• Prototype before duplicating.
• Keep each course outcome and completion rule explicit.

Connect the business path

Configure the required payment gateway, currency, taxes or tax service, pricing model, coupons, subscriptions or installments, emails, domain, analytics, and support channel using current documentation. Run test transactions and confirm account creation, access, receipt, cancellation, refund, and failed-payment behavior.

Document which system owns each customer and financial record. Avoid launching an integration simply because it is available; every connection adds credentials, failure modes, privacy work, and maintenance.

• Test payment and access separately.
• Keep a system-of-record map.

Run launch QA and preserve rollback

Test desktop and mobile enrollment, lesson media, downloads, assessments, messages, completion, reports, exports, SEO settings, legal pages, accessibility basics, and support. Use several learner states and a non-admin tester. Record expected and observed results with screenshots.

Back up source content and important exports, keep DNS and domain control accessible, and define how the team will pause sales or restore the previous path if a critical issue appears. Launch readiness includes recovery, not only the happy path.

• Use a dated regression checklist.
• Keep content and customer records exportable.

The 30-day free trial needs no credit card, but a trial school cannot use a custom domain.