# LMS Integrations

Honen is a full learning management system and can replace one outright, but it does
not have to. It also delivers into an LMS you already own, which means adopting it
does not require a migration.

There are four shipped paths, and they are independent and simultaneous.

## Choosing a path

You do not need to know which standard your LMS speaks. Pick the platform by name.

| You run | Path | Why |
|---|---|---|
| Canvas, Moodle, Blackboard, D2L Brightspace, Skilljar | LTI 1.3 | Deepest integration: automatic rosters, server-side grades |
| Cornerstone, Docebo, SAP SuccessFactors, Workday Learning, TalentLMS | SCORM | The package-based corporate systems |
| Google Classroom | Classroom add-on | Native, and better than LTI there |
| A Learning Record Store (Watershed, Learning Locker, SCORM Cloud) | xAPI or cmi5 | You want the full learning record, not one score per course |
| Anything else, or not sure | SCORM | Near-universal. Not being listed does not mean it will not work |

## What each path guarantees

| | LTI 1.3 | SCORM | Google Classroom |
|---|---|---|---|
| Setup | Admin handshake per platform | Download a package, upload it | Install the add-on |
| Rostering | Automatic | Learners created on first launch | From Classroom |
| Grade passback | Server to server | Browser-side, through the LMS's SCORM API | Server to server, as a draft grade |
| Instructor picks content inside the LMS | Yes | No | Yes |
| Re-deploy after a content edit | Never | Never | Never |

## LTI 1.3 and LTI Advantage

Connecting is, in practical terms, pasting a single URL. Once connected: rosters are
read from the LMS so there is nothing to import; groups and cohorts are created from
the LMS structure; learners never sign in to Honen separately because they are already
authenticated; and instructor, TA, learner and admin roles map into Honen roles.

Courses can run fully embedded, so the entire experience including the AI tutor runs
inside the LMS without anyone leaving, or as a one-click launch into a new tab already
signed in. Grades flow into the native gradebook, including AI-graded mastery rather
than a completion checkbox. Deep linking lets instructors pick content from inside the
LMS, and dynamic registration is supported.

## SCORM 1.2 and 2004: thin, live packages

You get the portability of SCORM without the frozen-snapshot tax that normally comes
with it. A Honen SCORM package does not contain a copy of your course. It carries a small
launcher that loads the live course inside the LMS. Edit the course in Honen and every
deployed package reflects the change immediately. You upload once and never re-upload
for a content change; only a settings change (audience, group, reporting policy)
requires a fresh export.

## Google Classroom

A native add-on rather than an LTI deployment, with attachment discovery inside
Classroom, graded coursework, ungraded links, materials and announcements. Grades are
written as a draft for the teacher to publish, scaled to the Classroom assignment's
point value. Copying a Classroom course carries the assignment scope and criteria
across, so two sections are never graded against different work.

## xAPI and cmi5

Three distinct capabilities:

- **Honen produces xAPI.** xAPI 1.0.3 statements are generated server-side for course,
  topic, activity, test and project events, stored in Honen, and optionally forwarded
  to your Learning Record Store with retry.
- **Honen serves an LRS.** Honen exposes the xAPI HTTP API (statements, activity state,
  activity and agent profile, activities, agents, about), authenticated with
  workspace-scoped credentials an administrator mints.
- **cmi5 export.** Thin packages that iframe the live course, provision the LMS
  learner, and relay the cmi5 statement sequence to the LMS's LRS while Honen keeps
  the same statements.

Both require an organization workspace and are available by default: the first cmi5
export materializes the configuration and provisions the launch tenant, in the same way
the first SCORM download does.

## Running several at once

Nothing is exclusive:

- One workspace holds as many LTI connections as it needs, each with its own keys,
  role mappings and grade policy.
- The same course can ship as SCORM 1.2 to one client and SCORM 2004 to another, plus
  packages targeting internal members and external learners separately. Each carries
  its own signed secret, so revoking one client's access does not affect the others.
- Separate tenants keep clients isolated and can bind a cohort to its own group.
- Exporting a package requires no LMS connection at all.

A single workspace can be LTI-connected to two universities, have SCORM packages in
five corporate systems, and run Google Classroom, all serving the same live courses
into the same analytics.

## Honen stays the source of truth

Every integration receives a projection of learner progress. No path lets an external
system write learning state back into Honen. The LMS gets a compliance-friendly
gradebook entry; Honen keeps the full mastery picture, with SCORM, LTI and xAPI
learners appearing in analytics alongside native members.

## Seats

Learners provisioned through any path are either internal members, who are normal
workspace members consuming a seat, or external learners, who are attached to a Honen
Site with a capped role and excluded from seat counts. Either way they are created
automatically on first launch and can claim a full account later.

## Boundaries

- SCORM gradebook writes happen from the browser while the learner has the course
  open. LTI and Classroom are server to server.
- Progress percent as a score policy is coarse: not started, started, complete.
- Certificates are issued per curriculum rather than per course.
- Session isolation is per tenant, not per learner, so two learners launching the same
  package in the same browser profile on a shared device share a session. Route
  cohorts to separate tenants, or use separate browser profiles. This matters for
  shared-device deployments.
- Package export requires an organization workspace.
- LTI 1.1, Common Cartridge and AICC are not supported. There is no importer, exporter
  or runtime for any of them; LTI 1.3 is the supported version.
- Honen produces xAPI and serves an LRS but is not an xAPI content player. Importing
  or playing a third-party xAPI or cmi5 package inside a Honen course is not
  supported.
- The LRS authenticates with HTTP Basic. OAuth 1.0a and signed statements as an
  authentication path are not implemented.
- A course exports as a single cmi5 assignable unit; per-topic units are not produced.
- Learners arriving without an LMS identifier are still tracked separately but appear
  as generated identifiers rather than names.

## Link LMS and SSO identities

Administrators can enable Use the same account for LMS and SSO logins on the LMS or SSO integration page.
Both controls change the same workspace setting. Automatic linking uses the same verified email for eligible accounts owned by the workspace.
Accounts outside that workspace are not linked automatically. A learner can link an LMS identity by signing in to the intended Honen account.
Test the complete launch and linking flow before rollout.
