Chat tools and AI assistants · Open to partnership

Microsoft Teams

Most Norwegian institutions run Microsoft 365, and for many staff Teams is where the working day happens: the chats, channels and meetings around a course. The route in would be a Teams app, a bot for conversation, or a message extension that pulls information into the compose box, installed the way any custom Teams app is: through the Teams admin center, not by an individual signing something on. It would reach the people running the course, not the students in it. None of it is built yet.

Not yet verified

  • There is no Teams app of either shape: no bot registered with the Bot Framework, no message extension, no app package.
  • Nothing has gone through the Teams admin center. An institution's app setup and permission policies would need to allow it before anyone could install it, and that conversation has not happened.
  • What a bot or message extension would be allowed to say about a named student's grading is not designed, beyond the standing rule that it would never be a channel a student is in.

How it connects

A Teams app reaches people two ways, and either could plausibly carry Lectora. A bot, built on the Bot Framework or Microsoft's newer Teams SDK, holds an actual conversation: someone asks it something in a chat or a channel, and it replies. A message extension is narrower: a search command a person invokes from the compose box to pull results into a message, or an action command that opens a small form. Both ship inside one app package, a manifest plus the bot or extension endpoint, and installing that package for an organization goes through the Teams admin center, where app setup and app permission policies decide who can add it and where, not a teacher clicking install on their own. Whichever shape it takes, it would sit in a chat or channel the course team already uses, never in a space a student can see. Lectora has no student-facing surface, and a grade or comment still reaches a student only through Canvas, under the educator's own Canvas identity. Nothing of this is built yet: there is no Lectora app in the Teams catalogue.

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.

Common questions

No. Those read course material through Microsoft Graph; this is about where course staff talk to Lectora. All three sit behind the same Microsoft 365 tenant and admin approval, but a Teams bot or message extension is separate work from a Graph file scope.

Related integrations