MaxIT · Beyond the LMS · AbilityLRS

Keep your LMS.
Strengthen your learning records.

AbilityLRS is MaxIT’s Learning Record Store for xAPI and cmi5 learning records. Bring activity and assessment evidence together, preserve a traceable history, and connect course results with compatible LMS platforms through LTI 1.3.

For compliance, learning technology and institutional teams · xAPI · cmi5 · LTI 1.3

The business problem

Does your learning record tell the whole story?

A status report is important, but an audit or investigation may require the history behind it: what happened, why training was assigned and how a completion was determined. AbilityLRS preserves the detail while your LMS continues to manage the learning experience.

01

Capture activity beyond a course

Receive xAPI statements from courses, simulations, assessments, applications and recorded in-person learning events.

02

Make completion rules explicit

Native cmi5 support manages registrations, sessions and course move-on rules, then passes a clear finished result to the LMS.

03

Preserve records you can examine

Tamper-evident history, administrative audit records and configurable retention support a more traceable learning record.

A practical approach

How does AbilityLRS fit your learning environment?

01

Connect

Register AbilityLRS with a compatible LTI 1.3 platform, or use it behind AbilityLMS.

02

Launch

Learners open cmi5 content from their LMS. LTI handles the identity handoff in that workflow.

03

Record

AbilityLRS receives the statements and evaluates the course’s cmi5 completion requirements.

04

Report

Status and scored results return through LTI Assignment and Grade Services. Detailed evidence remains in AbilityLRS.

Fit for your environment

Privacy and record integrity are part of the design.

AbilityLRS separates detailed learning evidence from the identity information needed to administer a learner. Tenant-level controls govern access, record retention and privacy choices.

  • Opaque learner identifiers by default, with identity mappings retained in the tenant
  • Customer data isolation and scoped access keys
  • Configurable storage region, encryption-key options and retention
  • Chained record fingerprints and independently timestamped integrity receipts

Questions, answered

What should you know about AbilityLRS?

What does a Learning Record Store do?

An LRS receives, stores and serves xAPI statements describing learning activity. AbilityLRS also supports cmi5 course launch and completion rules, with an emphasis on privacy and traceable records.

Does our LMS have to support cmi5 natively?

For the documented LTI workflow, no. AbilityLRS supplies the cmi5 player and record service through an LTI 1.3 connection. Your LMS must support the required LTI services and configuration.

Which LMS platforms have been tested?

MaxIT’s product documentation reports end-to-end tests with Moodle 4.5, Canvas and Sakai 25. Contact MaxIT to review your platform, version and required services.

What stays in the LMS?

The LMS receives completion status and gradebook results in the LTI workflow. AbilityLRS retains detailed xAPI and cmi5 history. Native AbilityLMS manages its own assignments, due dates, expiry and related rules.

Can records move between LRS platforms?

AbilityLRS supports forwarding, receiving and bulk exchange with conformant LRSs. Imported history remains LRS evidence and is not pushed into the LMS as new course completions.

How can we see AbilityLRS?

Request a demo to review your record sources, privacy needs and LMS integration. Talk to MaxIT about deployment and licensing for your environment.

Build on what you have

Explore the connected MaxIT solutions.

Start with the problem you need to solve. Add capabilities alongside the learning environment you already use.

See it in action

See the evidence behind the completion.

Bring your LMS and learning-record requirements. MaxIT will show the record workflow and discuss an integration and deployment approach.

Available for demos. Contact MaxIT to discuss pilot and deployment options.

})()