LTI integration: one record across LMS, SSO and HRIS

LTI opens an assessment inside the course; it doesn't decide where the record lives. How NUADU fits LTI, SSO, LMS, SIS and HRIS around one exportable record.

LTI integration lets a learner open an assessment from inside the course they already use, with the launch passing along who they are and which course they came from. It does not, on its own, settle the question an IT or compliance lead is asked: which system holds the record of each result, meaning how it came about and who signed it. Here is what LTI does, how NUADU's integration surface fits around it — identity, cohorts, results — and what that means for the deployment plan.

What is LTI integration?

LTI, short for Learning Tools Interoperability, is a standard for launching an external tool from inside a learning platform. LTI integration means a course in the LMS can open the assessment directly, and the launch tells the tool who the user is and which course they came from. The learner starts where they already work.

What is LTI in an LMS, then? The LMS is the platform that launches; the assessment platform is the tool that opens. On NUADU's side, the site states the integration surface in one line: LTI, SCORM, xAPI, REST API, SAML and OAuth, with direct integrations with major LMS and HRIS systems.

Assignments appear where learners already work.

LTI settles where the assessment opens. It does not settle which system is the system of record. A launch is a door, not a filing cabinet: the result, the marker who signed it, the override and its reason have to live somewhere and leave somewhere, in a form an auditor can read. Which system holds that record is also a procurement question, and the Trust & compliance page is where NUADU answers its data-protection half: the DPA, data residency options and sub-processors.

NUADU integrates with your LMS rather than replacing it. Whether an LMS quiz is enough on its own is a different question, taken up in how an LMS compares with an assessment platform.

What is the difference between SCORM, xAPI and LTI?

They solve different problems. SCORM packages learning content so that a learning platform can run it and track completion and score. xAPI records learning activity as statements sent to a learning record store, inside or outside a platform. LTI launches an external tool from inside a course. NUADU's site lists all three, alongside a REST API for systems that push cohorts or pull results directly, and SAML and OAuth for sign-in.

For an assessment platform, the useful question is not which acronym appears on a feature list but which job each one does in the systems you already run. The list is there so that the integration follows your estate rather than the other way round. None of the standards, on its own, is the record of who decided: a standard moves data, and the decision record is what the data has to carry out intact.

How do SSO and cohort import fit around LTI?

LTI gets the learner to the assessment; the identity and the cohort come from systems your institution already administers. Sign-in is SSO via SAML and OAuth. Cohorts come from the LMS, SIS or HRIS by LTI, API or SSO, with manual cohorts for a sitting that has no system of record yet, and region and department targeting where an organisation needs it.

This matters for the record as much as for convenience. A named educator at every decision point is only as good as the name. When sign-in runs through your directory, the name on a decision record is one your institution issued, not an account created on the day.

For certification bodies and public administrations, SAML, OAuth and custom API integrations are available, and NUADU integrates with sector or national identity systems where the integration has been agreed. Where agreed means scoped per deployment, not switched on by default.

For an HR or compliance lead, the HRIS is the roster, and a training platform with its own list of people is the second spreadsheet by another name. The same roster question comes up whenever the assessment is workplace training, as in assessing compliance training. Once a cohort is in, Assign handles exam scheduling and access control, with a dashboard that shows who received, started and submitted, per learner.

What is LMS integration, beyond the launch?

LMS integration is the set of connections that let a learning platform and the systems around it share people, courses and results, so that nobody keeps the same facts twice. For an assessment platform, the half that is easy to forget is the way out.

Three questions test any integration quickly. Where does the signed result go? In what format? And does the record of how it was reached travel with it? A grade in a gradebook answers the first question only. The other two decide whether an appeal or an audit can be answered from the exports, or only from screenshots and memory.

On NUADU, every AI output, override and approval is logged and reviewable, and that record can be exported alongside the results:

  • Reports export to PDF, CSV, BI tools or API.
  • Analysts get a REST API for data feeds, CSV/Excel export for custom analysis, and embeddable dashboard widgets for portals where appropriate.
  • Compliance teams get exportable evidence packages.
  • Credentials go out on open verifiable-credential standards, and a verifier does not need a NUADU account to confirm one.

That is the practical meaning of LMS/SIS integration for assessment, and it is the line the assessment platform for higher education page repeats: integrates with your LMS, SIS and SSO — no parallel record-keeping. Evidence that leaves the platform in a usable form is what an accreditation file needs; a dashboard that has to be screenshotted is not.

What this means for the deployment plan

Integration is the critical path, not a phase after go-live. A first full deployment takes 2–3 weeks, and the site attaches a qualifier that matters more here than the figure: deployment depends on integration with your LMS, SSO and learner records.

Where a connector doesn't exist out of the box, NUADU works with you to scope one. The most useful thing to bring to a first conversation is a short list: the identity provider, the LMS or HRIS that holds the cohorts, the system that must receive results, and the person who owns each. Where the site is silent — on a specific LMS, on how accounts are created and retired — so is this piece; that answer belongs in the scoping conversation.

Content is a separate track. Migrating an item bank covers the questions, rubrics and metadata; this piece covers people, identity and results. One record, not two.

→ Talk to us about your assessment workflow (30 min)