Choose your LMS

Odea connects to your LMS with LTI 1.3 Advantage for launching, and OAuth 2.0 for reading course materials and rosters. Pick your platform below. Each guide covers both credentials, in the order the screens have to be completed.

Brightspace (D2L)OAuth app, Dynamic Registration, deployment settings and org unit scoping.

CanvasAPI key for course sync, then the LTI key via Dynamic Registration.

MoodleOne-click setup with our plugin, or manual LTI registration.

Using Blackboard or something else? Email [email protected] and we will tell you where it stands.

What is the same everywhere

LTI setup takes about five minutes. Every platform we support uses IMS Dynamic Registration, so you paste one URL and the two systems negotiate every endpoint, key, and claim between themselves. There is no JSON to hand-edit and no values to copy back and forth. Allow fifteen minutes for a full setup including the OAuth credentials.

The registration URL is the same for all of them:

https://production-backend.odea.education/lti/register

We request three claims. The issuer, a stable user identifier, and the user’s email address. Your LMS also sends the course context and the user’s role with each launch. Nothing else.

No grade or roster scopes are requested by the LTI tool. Assignment and Grade Services and Names and Role Provisioning stay off.

Odea opens in a new tab. Sign-in uses a secure cookie exchange that browsers only permit in a top-level browsing context. Canvas and our Moodle plugin set this automatically; on Brightspace and manual Moodle you set it yourself.

Course copies are handled. Odea resolves the course from the launch every time rather than binding it to the link, so a copied course is treated as new: the educator re-runs a short setup, and students see a clear “not set up yet” page until then. Launches never break and never serve the previous term’s content.

What differs

	Brightspace	Canvas	Moodle
REST API OAuth (step 1)	Required	Required (API key)	Web service token
LTI registration (step 2)	Dynamic	Dynamic	Plugin, or Dynamic
New-tab launch	You set it	Automatic	Plugin sets it
Objects to configure	OAuth → Registration → Deployment → Link	OAuth → LTI key	Plugin handles both
Auto-verified institution	Only on your own domain	Only on your own domain	Most self-hosted sites

Institution verification

When your LMS runs on a vendor-shared domain (*.brightspace.com, a shared Instructure address, shared Moodle hosting), that address identifies the vendor rather than your school, so we cannot confirm which institution a registration belongs to. Those go to a person for review and are usually confirmed within one working day.

On your own institutional domain, verification is automatic and the connection is live immediately.

Before you start

You need administrator access to your LMS. If you are a lecturer wanting Odea in your course, your LMS administrator does this part once for the whole institution, send them this page.

For Canvas and Brightspace, step 1 of your platform guide creates the OAuth app. The LTI registration in step 2 asks for the client ID and secret it produces, so the steps have to be done in order.

Nothing here requires a change to your identity provider, and no firewall rules are needed: your LMS calls us over standard HTTPS.