LTI-Only Access

Ragtime speaks LTI 1.3, so an assistant can be launched from inside an LMS (Moodle, Canvas, Blackboard, …) as a graded/tracked activity, with seats and launch history.

Set up the LTI connection

Under Dashboard → Deployment → LTI, connect Ragtime to your LMS platform (register the platform, exchange keys). Seat assignments and launch history are managed here and in the Seats panel.

Also see the full LTI 1.3 integration docs for the technical setup.

Make a device LTI-only

To ensure an assistant can only be reached through an LMS launch — and never via a bare public link:

1. Go to Dashboard → Deployment → Devices and edit the device.
2. Enable LTI-only access.
3. Save.

With this flag on, opening the device’s normal published URL directly returns an error:

“This experience is available only through your LMS launch.”

Access is granted only when the learner arrives through a valid LTI launch — Ragtime verifies the launch and hands the session an LTI context via a secure bridge cookie.

Tip

This is the cleanest way to keep an assistant private to a course cohort: the LMS is the only door in. Combine it with seats to meter and license access per learner.

When to use LTI-only vs. other access models

Scenario	Recommended approach
Course activity, only enrolled learners should access	LTI-only on the device
LMS delivery, but the link should also work outside the LMS	Leave LTI-only off; set up LTI for tracking but keep the public link open
Legacy LMS without LTI 1.3 support	Use a SCORM package instead
Named individuals, each with personalized instructions and metered budget	Use a Campaign