New: Original View reports — findings directly on the original document See what's new
Integrations & LTI

Native to your LMS, open to everything else

iOriginally launches from Moodle, Canvas, Blackboard, Brightspace and any LTI 1.3-compliant LMS — with single sign-on, automatic role mapping, and a REST API with signed webhooks for everything the LMS doesn't cover.

LTI 1.3-native launchSSO with automatic role mappingTypical setup: an afternoon
LMS integrations

One registration, every course

iOriginally is an LTI 1.3 tool, not a per-LMS plugin. Register it once in your admin panel and every course on campus can launch it — the same protocol whether you run Moodle or Brightspace.

Moodle

Register iOriginally as an external tool once; instructors add it to any course as an activity and roles carry through automatically.

Canvas

Launch from Canvas courses without a second login — instructors and students land in the right workspace, already signed in.

Blackboard

One LTI 1.3 registration in Blackboard Learn connects every course; submissions and reports stay in the course context.

Brightspace

D2L Brightspace connects through the same standard LTI 1.3 registration — one protocol, no bespoke plugin to maintain.

Any compliant LMS

iOriginally implements the LTI 1.3 standard itself, so any compliant platform — commercial or open-source — connects the same way.

Single sign-on

Sign-on through your institution's identity provider, with automatic role mapping for instructors, students and administrators.

One standard, not six plugins: iOriginally connects through LTI 1.3 itself, so there is no bespoke per-LMS plugin to install, patch or re-certify every time your LMS upgrades.
Setup

Connected in an afternoon

LTI registration plus SSO is a standard admin task, not an IT project. The docs walk your LMS administrator through each platform step by step.

1

Register the tool

Your LMS administrator adds iOriginally as an LTI 1.3 tool — a standard registration in the admin panel, covered step by step in our setup guides.

2

Connect sign-on

Point single sign-on at your identity provider. Roles map automatically, so instructors, students and administrators each land in the right workspace.

3

Launch from a course

Instructors add iOriginally to their courses, students submit where they already work, and reports open in the same course context.

1 afternoon
typical setup — LTI registration plus single sign-on
LTI 1.3
one open standard, the same registration on every LMS
0
separate passwords to provision once SSO is connected
4+
major LMS platforms, plus any LTI 1.3-compliant one
Identity

Single sign-on, with roles that map themselves

Nobody provisions accounts by hand. When someone launches iOriginally from the LMS or signs in through your identity provider, they arrive in the right workspace with the right permissions — automatically.

  • SSO through your identity provider — one set of institutional credentials, nothing new to issue or reset.
  • Automatic role mapping — LMS instructors become instructors, students become students, admins get admin. No manual assignment.
  • Departments and roles respected — integrity office, instructors, students and administrators each see exactly what your policy allows.
  • Every access audited — sign-ins and role changes land in the audit log alongside every report action.
How we protect institutional data
Professor working on a laptop in a lecture theatre
Data in, data out

A REST API for everything the LMS doesn't cover

Institution-scoped API keys come straight from your settings — no sales call to get credentials. Automate submissions, listen for results and export what your analysts need.

REST API

Automate submissions and pull results from your own systems. API keys are institution-scoped and generated from your settings — create, rotate and revoke them yourself, no support ticket required.

Institution-scoped keysRotate anytime

Signed webhooks

Get notified the moment a report completes instead of polling. Every webhook payload is signed, so your systems can verify it really came from iOriginally before acting on it.

Signature verificationReport events

CSV export

Export submissions, scores and audit trails as CSV for your data warehouse, institutional research office or accreditation evidence packs — no API work needed.

Analytics-readyAudit trails
Docs before contracts: the LTI, SSO, API and webhook setup guides are published in our docs, so your technical team can evaluate the integration before you ever talk to sales.

Connect your LMS this term

Book a demo and we'll walk your LMS administrator through LTI registration and single sign-on — most institutions finish setup in an afternoon.