Learning management systems · Coming soon
Brightspace
Brightspace is D2L's LMS, and it launches an LTI 1.3 tool through a two-step process that is stricter than most: a Brightspace admin first registers Lectora under Manage Extensibility to get a client ID and issuer, then creates a separate deployment and picks exactly which Org Units, meaning departments, terms, or individual courses, can actually launch it. Brightspace also lets each institution map its own roles onto the launch on that same screen, so what a launch actually says about a user is a local decision rather than a fixed vocabulary. Neither step has been done for Lectora.
What works today
- Lectora launches as a standard LTI 1.3 tool, which is how Brightspace expects an external tool to arrive once it is registered and deployed.
- The launch parser accommodates admin-configured role URIs rather than assuming one fixed vocabulary, which matches how Brightspace's own role mapping works.
Not yet verified
- No Brightspace pilot has run, so no institution's role mapping has been validated in practice.
- Lectora has not been registered under Manage Extensibility on any Brightspace instance, so there is no issuer, client ID or deployment to test against.
- Grade publishing and roster sync are unverified against Brightspace specifically.
How it connects
Brightspace separates registering a tool from deploying it. An admin first goes to Admin Tools, Manage Extensibility, LTI Advantage, and registers Lectora to get back an issuer, a client ID and the other values Lectora would need to complete the handshake. A second step, a new deployment under External Learning Tools, is where the admin picks the Org Units, department, term, or a single course, that the tool is actually allowed to launch in. The same screen is where Brightspace's per-institution role mapping lives: an admin decides which of their own roles count as which LTI role, rather than Brightspace sending one fixed vocabulary the way Canvas does. Nothing has been registered or deployed for Lectora yet, so none of this has been exercised against a real Brightspace instance.
Data and access
Lectora reads only what the assessment needs, and writes nothing back until an educator approves it. The Canvas access page documents the full scope, and our privacy policy, subprocessors and DPA cover the legal side.