Sign-up, attendance and certificates
in the same system.

For a typical course administrator coordinating 50–200 courses a year: expected savings are 30–60% of admin time per course. The time sinks that disappear are manual sign-up confirmations, Excel exports for participant lists, Word mail-merge for reminders, manual sending of certificates and back-and-forth with payments. The figure depends on how much you've already automated — give us a picture of your current flow and we'll work it out concretely.

No — that's exactly why templates exist. You set up one carefully built course (settings, email templates, price structure, certificate template, custom fields), turn it into a template, and new courses start from the template. If you change the template later, you choose whether changes apply to future courses or also retroactively to existing ones.

Yes — that's the whole point of the roles. The Instructor role sees the participant list, registers attendance and uploads materials, but can't change prices, refund payments or delete the course. The Subject lead gets edit access on content without seeing payment data. The Observer role is pure read access for leadership or auditors. Roles can also be set per course — so an instructor is admin on their own course but observer on others.

AlonLearn runs on AWS in the EU (Ireland). Participant data, attendance logs and certificates stay within the EEA. A data processing agreement and GDPR addendum are signed at onboarding. Participants have full right of access and can delete their own data via My page; deletion respects the Accounting Act's retention obligation for payment data. The audit log shows who has seen and changed what — critical when courses must be auditable.

The participant cancels themselves via My page if it's within the cancellation deadline you've set. When the cancellation is registered, four things happen automatically: the seat is released, the next person on the waitlist gets an automatic offer with a payment link, a refund is triggered if the rules say so, and a confirmation goes out. You don't have to do anything. If it's outside the cancellation deadline, the request lands in your queue with all context — deadline, payment, communication history — so you make the decision, not an email chain.

Yes. Multiple administrators can work in the same course without overwriting each other — changes are logged per user. You see who last changed what, and the audit log tracks activity across the course. Especially useful when a coordinator sets up the course and a subject lead makes content adjustments in parallel.

Either way — you choose per course. Open courses live in the course catalogue and participants find and sign up themselves. Closed courses you roll out to a specific audience (department, professional group, employee list), and only those invited see the course. For internal courses where HR enrols everyone, you can import CSV — or let AlonLearn's "audience" function enrol automatically based on rules.

Course administration is the core of every AlonLearn package — you don't pay per course, but per number of participants in the platform. That means a gradual expansion of your course catalogue won't produce an unexpected jump in the bill. Packages start at 7,500 NOK/month. Give us the number of participants and how many courses you run annually, and we'll build a tailored quote.