Panova is an LTI 1.3 tool. Once registered, instructors place
experiences directly into courses and results flow back
automatically.

## Registering

Two routes, from **Organisation → Integrations**:

- **Dynamic registration** — paste Panova's registration URL into your
  LMS and it exchanges the details itself. Supported by Canvas, Moodle
  and Blackboard among others, and much less error-prone.
- **Manual** — copy Panova's client id, keyset URL, login and launch
  URLs into your LMS, and paste six values back: its **issuer**,
  **client id** and **deployment id**, and its **authorisation**,
  **token** and **key set** addresses. Use this if your LMS does not
  support dynamic registration.

Each registration is scoped to your organisation. Two organisations
can connect the same LMS independently without seeing each other's
content.

> Connecting is done once per LMS. After that a teacher adds an experience to a course without coming back here.

## Placing an experience in a course

In the course, add an external tool and choose Panova. The **content
picker** opens with the experiences that workspace can reach; choose
one and it is attached to that assignment.

The course link then follows every future publish. Where a cohort
must be assessed against identical content, give them a version's own
link instead of the plain one — see [Sending a class to one
version](/support/articles/sending-a-class-to-one-version). There is
no live-or-frozen choice in the content picker itself; that setting
lives in the **Share** dialog and applies to everybody at once.

## Grades

If the assignment is graded, Panova posts a result back when the
learner has completed everything you placed — one grade per
experience, as a 0–1 ratio your LMS scales to its own points.

Progress shows as **Started** until every activity has been submitted.

## If a grade is refused, somebody is told

A gradebook column that never fills in used to be found by a student
asking why they had no mark. Now, when the platform refuses a result —
a revoked permission, a line item that has been removed, a deployment
that has expired — the workspace's leaders and the organisation's
admins get a notification naming the learner and the experience.

The learner's work is safe either way; it is only the gradebook entry
that is missing. Fix the connection and re-check the column.

You get **one** line per failure, not one per learner: a broken
connection fails for the whole class, and thirty copies of one fact
make it unreadable. Once you have marked the line as read, the next
failure tells you again — which is what you want, because it means the
thing you went and fixed is still broken.

## If a launch fails

A launch that cannot be verified shows an explicit error rather than a
login page. The usual causes are a clock skew between the two systems,
a stale keyset, or a registration pointing at a different environment.

Two refusals are deliberate and are worth telling apart from a fault.
**A disconnected LMS cannot launch**: pressing **Disconnect** on the
Integrations screen ends every launch from that platform, and a course
still pointing at Panova gets an error rather than a lesson. And **a
plan that no longer includes LTI cannot launch either**, whatever was
registered while it did.

## Availability

LTI is included on Professional and Enterprise plans.