Notes, documents and course material · Coming soon
Notion
Notion holds the pages and databases institutions actually write course material in: lecture notes, worked examples, rubric guidance, reading trackers built as databases rather than folders of files. Today you can paste that content in and it survives the trip. The real route in, when built, would be Notion's own integration API: a workspace owner shares specific pages or databases with a Lectora connection, one at a time, rather than handing over the whole workspace.
What works today
- Content pasted from a Notion page keeps its headings, lists and tables instead of collapsing into flat text.
Not yet verified
- There is no Notion connection: no integration token is registered, and no page or database has been shared with one.
- Nothing syncs. Pages and databases are not read automatically, and an edit in Notion does not reach Lectora until someone pastes it again.
How it connects
Notion's own API is scoped per page or database, not per workspace. An internal integration gets a token, but the token can see nothing until someone opens a page's or database's "•••" menu and adds the integration under Connections; a page shared this way passes its access down to its child pages automatically, and an Enterprise workspace can further restrict which pages a connection is allowed to reach at all. Built, this would mean a course owner choosing exactly which pages or databases Lectora can read, granted with a read-only capability, rather than an all-or-nothing grant to the workspace.
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.