Skip to content
Contact support

How the LMS integration works

For LMS administrators

This page explains what an Odea connection does at your institution. It covers what is the same on every LMS, then lists where the platforms differ. It contains no setup steps, so you can forward it to anyone reviewing the integration. The steps are in the guide for your LMS.

  • Two connections. One lets people open Odea from a course. The other lets Odea read that course’s materials and class list.
  • Educators decide. Installing Odea reads nothing. A course is only read once an educator on that course connects it.
  • Read, not write. Odea does not change your course content or grades. The one exception is an optional Odea module on Canvas.
  • Students need no new account. They click Odea in their course and are signed in.
  • Your LMS stays the source of truth. Change a course in the LMS, and the next sync brings Odea in line.

Sync is the centre of the integration, because it means nobody runs a second system. Odea mirrors the course you already have. Your LMS stays the place where staff work, and Odea follows it.

Work a separate platform would create What happens with Odea
Uploading materials a second time Materials arrive from the LMS
Rebuilding the course structure Folders follow the LMS modules
Maintaining class lists Enrolments follow the LMS
Creating accounts and passwords Students arrive through the LMS
Assigning roles Roles come from the LMS
Withdrawing outdated material Items removed from the LMS leave at next sync
Managing leavers People off the class list leave at next sync

This changes the day-to-day work for three groups:

  • Your LMS team gets no new user administration. There are no accounts to provision and no separate class lists to reconcile. After the one-time setup, the integration needs no routine maintenance.
  • Educators keep working as they do today. They update a course in the LMS, and that update reaches Odea. They do not learn a new place to publish.
  • Your institution keeps one source of truth. Decisions about who may see what are made in the LMS, under the rules you already have, and Odea follows them.

Every integration has the same two parts. Each can fail without affecting the other, which is why a setup can launch correctly and still show no materials.

Launch connection Content connection
Technology LTI 1.3 (Learning Tools Interoperability) Your LMS’s REST API
What it does Opens Odea from a course and proves who the user is Reads course materials and the class list
When it is used Each time someone clicks Odea Each time a course syncs
Who uses it Everyone: students and staff Educators, or the plugin’s web service on Moodle
If it is missing Nobody can reach Odea from the LMS Launches work, but no materials arrive

Your administrator sets up both once for the whole institution. No change to your identity provider is needed, and no firewall rules are needed.

A sync reads the course, its structure, its materials and its class list.

From your LMS In Odea
Course The Odea course
Modules and sections Folders, with the same structure
Files Course materials the AI can use
Course pages Readable content, except on Moodle
Class list Enrolments, with roles mapped from the LMS

Only what students can see. Unpublished or hidden content stays out of Odea. If a student cannot see an item in the LMS, it is not synced.

Educators can narrow it further. Sync brings the whole course across. Manual Sync lets the educator pick modules, pages and files. Choosing a page also brings in the files that page links to, with no separate approval.

File types. PDF, Word, PowerPoint and plain text files sync on every LMS, up to 100 MB per file. Files in other formats are skipped, and the rest of the sync carries on.

What Odea does not read: grades, assignments, quizzes and tests, discussions, announcements, messages, or external tools embedded in a course.

What Odea writes back: nothing on Blackboard, Brightspace or Moodle. On Canvas, the sync can add an Odea module so students can open Odea from the course. Grades are never written back.

Trigger What happens Available on
First connection An educator connects the course, and Odea reads it for the first time Every LMS
Refresh by an educator An educator refreshes the course from Odea at any time Every LMS
Scheduled sync Odea refreshes courses at 08:00, 12:00 and 16:00 Central European Time on weekdays Every LMS

Opening Odea never syncs. A launch only signs the user in, so a change in the LMS does not appear because someone clicked the link.

Scheduled sync is off by default. You switch it on for the institution under Admin dashboard → Settings. Educators can still refresh a course by hand when a change should appear before the next run.

Processing takes time after a sync. Each file is read and indexed before the AI can use it. Most finish within a few minutes, and large batches take longer. If a file fails, the rest of the course is unaffected, and we fix it and resync it within 24 hours. Educators do not need to act.

Odea compares the LMS with its own record and acts only on the difference.

  • New items are added.
  • Changed items are processed again.
  • Items removed from the LMS are removed from Odea.
  • Students who left the class list lose their enrolment in that Odea course.
  • Materials an educator uploaded in Odea stay, because they did not come from the LMS.
  • People enrolled by hand in Odea stay, for the same reason.
  1. An educator clicks Odea in a course that is not connected yet.

  2. Odea opens a setup page listing the courses that educator teaches.

  3. If this is their first time, the educator authorises Odea to read the LMS for them. On Moodle the plugin’s web service handles this, so there is no such step.

  4. The educator presses Sync or Manual Sync, chooses the language for AI-generated content, and starts the sync.

  5. Odea reads the course and processes its materials.

This happens once per course. Every launch after that goes straight into the course.

Whose permissions apply. On Blackboard, Brightspace and Canvas, Odea reads with the connecting educator’s own LMS permissions, so it reaches only the courses that person can reach. An educator who has not authorised Odea can have a course read through a colleague’s connection, but only if the LMS lists them as staff on that course or they are an Odea administrator at your institution. That covers reads only.

Course copies and new terms. A copied course has a new identity in the LMS, so Odea treats it as a new course. The educator repeats setup, and students see the “not set up yet” page until then. Launches never serve the previous term’s materials.

Students need no invitation, registration or Odea password.

  1. The student clicks Odea in their course. It opens in a new tab.

  2. The LMS sends Odea a signed message with the student’s identifier, email address, role and course.

  3. Odea verifies the signature and checks the email address against your institution’s registered domains.

  4. Odea finds the student’s account, or creates it on their first visit.

  5. Odea places the student in the course and signs them in.

Class lists and launches work together. A sync imports the class list in advance. A student who joins after the last sync is enrolled the first time they launch, so nobody waits for a sync to get in.

Roles come from the LMS. Nobody assigns them by hand.

Role in your LMS Role in Odea
Instructor, Administrator, Content Developer, Manager, Officer Educator
Teaching Assistant, Mentor Educator Assistant
Anything else, or no role sent Student

An unrecognised role always falls back to Student, never to a role with more access.

Three situations stop a launch:

  • The course is not connected yet. The student sees a “not set up yet” page, with no error and no access to any other course.
  • The LMS sends no email address. Odea needs the address to identify the person, so the launch is refused.
  • The email domain is not registered to your institution. The launch is refused and we are notified. See Troubleshooting LTI launches.
Blackboard Brightspace Canvas Moodle
Launch setup Application ID from Odea Dynamic Registration Dynamic Registration Plugin, or Dynamic Registration
Content access OAuth, per educator OAuth, per educator OAuth or access token, per educator Web service token, per site
Structure read Folders and learning modules Modules Modules Sections
Pages Ultra documents HTML topics Canvas pages, with their images and YouTube videos Not synced
Files Files and item attachments File topics Module files File resources
“Visible” means Available to students Not hidden Published Visible and available to the user
Writes to the LMS Nothing Nothing Optional Odea module Nothing
Opens in a new tab You set it You set it Automatic Plugin sets it
  • Received per launch: issuer, a stable user identifier, email address, role and course context. Odea does not use the person’s name from a launch.
  • Received through the content connection: course materials and class lists, for the courses educators choose to connect.
  • Not requested: LTI grade services and LTI roster services stay off.
  • Hosting: processed and stored in the EU on Google Cloud. Encrypted in transit (TLS 1.2 and above) and at rest (AES-256).
  • No data resale, no advertising, no behavioural monetisation, as a contractual commitment.

Full detail is in the Trust Center and the privacy policy.

Questions from your security or procurement team? Email [email protected].