Academies, courses and classes
Group your offer into an organised hierarchy. Classes manage groups of students, while modules and lessons provide the sequence within a programme. Teachers work on the courses and materials assigned to them.
BEETLEWEB
Entering the network
Lumera / Learning platform & CRM
Learning, people and content.
One connected workspace.
Lumera brings together the tools to organise an academy, deliver learning programmes and manage relationships with students and contacts. Courses, progress, community, editorial content, email campaigns and commerce share a modular web platform, with access tailored to each role.
An academy works with more than lessons. It needs to organise enrolments, assign teachers, publish resources, understand how students are progressing and maintain a relationship with its audience. Lumera brings these activities into a shared working environment.
It is designed for training organisations, academies and teams delivering structured learning programmes. Students access their own courses and materials; staff work with the tools permitted by their role. Public content, contact collection and product sales extend the platform around that learning experience.
01 / How it works
The platform connects preparation, access, learning and follow-up. Here is a typical workflow, configured around the way your organisation works.
Organise your academy into courses, classes, modules and lessons. Add teaching materials, define the order of the content and prepare quizzes and completion rules before publication.
Create or manage user accounts, assign the appropriate roles and enrol students in their classes. Registration and email verification are also part of the account workflow; access to learning content remains subject to enrolment and permissions.
Students open their available courses, follow lessons, consult materials, save personal notes and work towards their goals. The platform records learning activity and quiz results to make progress visible.
Authorised staff can review progress and manage the learning structure. Where a course enables certificates, eligible students receive a completion record. Community discussions and configured communications support the next steps.
02 / Learning
Lumera links the content of a course to the people who can access it and to their recorded activity. Teaching and administration work from the same course structure.
Group your offer into an organised hierarchy. Classes manage groups of students, while modules and lessons provide the sequence within a programme. Teachers work on the courses and materials assigned to them.
Prepare lessons, manage their publication state and order, and attach resources such as documents, images, audio and video. Materials are served through access checks, according to the learner’s authorisation.
The platform records lesson activity, including playback position and viewing time where supported. Completion is checked against the rules defined for the content; merely opening a lesson is not equivalent to finishing a programme.
Create assessments, collect answers and record attempts and outcomes. Passing requirements contribute to the learning journey and, where configured, to certificate eligibility. Staff can use these results to understand progress.
Students can save notes and define goals within their account. These provide continuity between sessions and a place to organise reflections alongside the courses they are following.
Eligible courses can issue certificates with a downloadable PDF and a verification code or QR code. Verification checks the record and document integrity; authorised staff can revoke a certificate when necessary.
A certificate records completion under the organisation’s configured rules. The verification feature does not, by itself, make a course an accredited qualification.
03 / People
A student, a teacher and an administrator have different responsibilities. Lumera applies access controls on the server as well as adapting the interface.
Access authorised courses and lessons, consult resources, complete quizzes and review personal progress. Their account also holds notes, goals and certificates, together with access to purchased digital content where available.
Prepare and maintain assigned courses, classes, modules, lessons and materials. They can review the learning activity available to their role and work with their assigned groups.
Manage permitted user operations, class assignments and operational activities. Dedicated tools cover editorial content, contact lists, campaigns and commerce, according to the configured permissions.
Oversee platform configuration and the areas available to their role. The top-level administrator also controls capabilities, audit access and system settings reserved for that level.
The community provides discussions, replies and reactions. Moderation settings and a read-only mode help staff manage participation; access and publishing rules depend on the platform configuration.
04 / Content & CRM
The editorial and CRM tools connect the public-facing part of a project with the team managing its audience. Publishing an article, collecting an enquiry and sending an email each have a dedicated workflow.
Create articles with a visual editor, organise categories and images, and manage drafts, publication and scheduled releases. Page layouts, calls to action and search and social metadata help prepare content for the connected public site.
Build subscription forms with custom fields and embed them in articles or landing pages. A form has an associated contact list and campaign. Subscriptions, consent and withdrawals are tracked separately from the public content.
Prepare several messages in a campaign, sent after a delay from subscription or at a fixed date and time. Queue status, retries and delivery feedback help staff follow processing; unsubscribe links allow contacts to leave the list.
Organise opportunities into configurable pipelines and stages. Record contact information, source, estimated value, probability, expected closing date and notes. Search, filtered lists and bulk operations help the team manage follow-up.
Scheduled publishing and email sending require server jobs. Email delivery also requires a configured and tested provider, domain authentication and feedback handling; creating a campaign alone does not activate delivery.
05 / Commerce
The commerce module manages physical and digital products, connecting the catalogue to orders and to the content available in a customer’s account.
Create product listings with descriptions, covers, tags and prices. Physical products have inventory and shipping information; digital products have associated content and access rules.
The server calculates the order and the platform includes an adapter for hosted Stripe Checkout. Payment processing needs a configured account, credentials and verified HTTPS webhooks before live use.
Manage order states, stock reservations, shipping rates and shipments. Return and refund workflows are also provided; their operation depends on the order state and the configured payment services.
Authorised digital purchases appear in the user’s library, with content opened through the platform’s reader. Access is linked to the account and entitlement: purchasing a product does not necessarily mean receiving an unrestricted file download.
06 / Personal support
Personal goals, notes and learning progress provide continuity to a student’s journey. The project also includes a separate coach module, whose current behaviour should be distinguished from a generative AI service.
When the optional module is enabled, the user explicitly chooses its permissions. It includes revocable consent, preferences and personal memories that can be created, edited, archived or deleted.
The current implementation provides guided responses based on predefined rules and does not connect to an external AI provider. The module is disabled by default; a future model integration would require separate implementation, configuration and validation.
07 / Setup
Lumera runs on a web server and is accessed through a browser. Setup includes the learning organisation, user permissions, content, external services and operational procedures.
Map courses, classes, staff responsibilities and student access. Choose which modules are needed and prepare the content and communication flows before opening the platform to users.
Set up hosting, databases and HTTPS, then connect the email and payment services required by the project. Test scheduled jobs, account flows and external callbacks in the deployment environment.
The architecture uses MySQL or MariaDB for identities and operational records, and SQLite for teaching and editorial content. Server-side authorisation, protected sessions and administrative audit events support access control.
Include databases and uploaded files in the backup plan. The project supplies encrypted backup and validation tools; schedules, protected key storage, restore procedures and monitoring must be organised for the actual installation.
Account tools include data export and erasure requests, with an administrative processing workflow. Retention choices and the organisation’s privacy processes must be defined for its actual use of the platform.
08 / FAQ
Training organisations, academies and teams that need to organise learning and manage the people around it. The combination of learning, CRM, editorial content and commerce is useful when these activities belong to the same project. The modules and workflows should be selected around the organisation’s actual needs.
Lumera is a web application accessed through a browser. Students need an account, a connection and permission to access their content. No separate desktop installation is required for the web platform.
Yes. Course and class assignments define the areas available to teachers. Server-side checks also protect lessons and materials, so access depends on the assigned role and learning scope.
Not on its own. Certificate issuance depends on the course settings and eligibility requirements, including the relevant completion and quiz conditions. The platform can then provide a PDF and a way to verify its status.
The application includes the corresponding modules, but external services need configuration and testing. Email requires a delivery provider and scheduled processing; online payment requires a payment account and verified callbacks. Availability depends on the deployed configuration.
The current optional coach module uses predefined guided responses and has no active external model integration. It includes consent and memory controls, but should not be described as a fully operational generative assistant.
The modular architecture includes a dedicated server-to-server gateway with signed requests and capability checks. Each integration needs explicit configuration and development against the available operations; it is not a ready-made connector for every external service.
Start with the learning offer, user roles, existing content and required services. Then define the module configuration, hosting, any data migration and acceptance checks. An initial discussion helps establish a realistic implementation scope before rollout.
Courses, people, content and services: let’s define the Lumera configuration that fits your project.