Frequently Asked Questions

The platform takes on the whole training cycle: assigning courses by position or unit, deadline reminders, assessment, recording results and issuing certificates. Instead of a paper register and spreadsheets, the institution gets a single source of truth for who completed what, when and with what result.

Reporting is automated separately: analytics is produced by unit, grade of position and period, so preparing a report for management stops being a job that takes days.

Yes. The structure of the institution is carried into the platform as a hierarchy of course categories and user groups: central office, regional bodies, directorates and departments. Each unit gets its own set of courses and its own training officer.

For organisations with a regional network this is the main scenario: one LMS serves both the central office and the regional units. A local manager sees only their own team, while the central office sees the consolidated picture.

Yes. Professional development for civil servants is built as a programme of several courses with their own deadlines, a pass mark and a final assessment. The platform records attempts, scores and the completion date, and issues a certificate.

Assessment is configured separately from the learning materials: a question bank, random selection, limits on time and attempts. A learning history is kept for every employee and is available to the responsible officer.

Yes, and this is one of the reasons Moodle is chosen for the public sector. The standard roles — administrator, instructional designer, manager, learner — are extended with custom ones that match real positions and areas of responsibility in the institution.

Rights are granted not “to the system” but to a specific context: a course category, a single course or a group. A training officer in a regional unit therefore works only with their own users.

Yes. Integration is done through the platform's REST API, webhooks or a middleware service. The most common scenarios are single sign-on through a corporate account (Active Directory, LDAP, SSO) and synchronising users and the structure of units from the HR system.

SCORM, xAPI and LTI cover external learning content. The exact list of integrations is defined during requirements analysis, depending on the systems the institution already runs.

Yes. Courses, learning materials, the user base and completion history are all migrated. Where materials currently exist as documents, presentations and video, they are assembled into structured courses; where they sit in another LMS, export in standard formats is used.

Migration is run as a managed project: first a test transfer on a copy, then a data reconciliation, and only after that the launch in production. A rollback plan is prepared in advance.

Out of the box you get reports on course progress and completion, assessment results, user activity, the gradebook and action logs. They can be filtered by unit, group, course and period, and exported to a file.

Where the institution needs a report format the core does not provide, we develop a custom one — for example a summary of mandatory programme completion broken down by regional unit.

Yes. Moodle support runs under an SLA and covers core and plugin updates including security patches, performance monitoring, incident response and consultations for the institution's administrators.

Platform development is handled separately: new courses and units, additional integrations and reports. The corporate training system we modernised for a leading Ukrainian bank, for example, stayed under our support after launch.