For the small things your LMS should do better.
Useful LMS apps.
Your institution stays in control.
Give instructors small tools for everyday teaching. Lantern runs reviewed apps through one LMS integration. Your administrators approve what each app can access and inspect the audit trail.
Your administrators must approve LMS access.
Introduction to environmental studies
Put names to faces in your course.
- Amelia Santos Learner
- Nathan Brooks Learner
- Lina Chen Learner
- Theo Martin Learner
- Leila Patel Learner
- Alex Kim Learner
LMS connections
- Canvas
- Moodle
- Brightspace
- Sakai
Our first app
Start with the people in your course.
Photo Roster shows course members' names, roles, and available profile photos in a readable grid. Instructors open it from the LMS. Lantern handles LMS access, so the app never receives an LMS token.
Photo Roster uses Lantern's shared roster, permission, photo, and audit services. Your next app can use the same services.
Set up your institutionWhat Photo Roster can access
- Course roster
- Names, standardized roles, and membership status from your LMS.
- Protected photos
- Lantern checks photo permissions and gives the app short-lived image access.
- Approved fields
- The app declares the fields it needs. Your administrators approve each permission.
- Photo source
- Photos come from the LMS profile picture field. Lantern has no separate campus ID photo connection.
The current Photo Roster package requests roster, photo, and email access. Your administrators must approve all three before activating it.
For campus teams
Your institution decides what each app can do.
Review an app, approve its permissions for your institution or a specific course, then activate that version. Revoke a permission or disable the installation when access needs to change.
Review the security controls- Approve the exact version
- Your approval applies to one app package version. A new version needs new approval.
- Keep credentials in the platform
- Lantern runs reviewed Worker apps without LMS tokens, database bindings, or unrestricted network access.
- Inspect app access
- Lantern records access decisions and LMS service calls in a linked audit trail. These records omit roster names, emails, and photo URLs.
Build apps on a shared LMS layer.
Use Lantern's typed services for roster access, opaque subject IDs, and protected photos. Lantern checks permissions and handles the LMS connection.
Reviewed server apps and AI-built browser activities use separate runtime contracts. Neither receives LMS credentials.
Read the app authoring guide- Roster access
- Read course members through one permission-checked service.
- Protected media
- Display photos without receiving the LMS image URLs.
- App permissions
- Your administrators approve each app version's capabilities and scope.
- Audit trail
- Follow access decisions and service calls through a shared trace ID.
Cloudflare Workers isolate reviewed server apps. Lantern gives them approved services and handles the LMS integration.
What's available
and what's next
Built now
Photo Roster and the services it uses: institution-owned LMS connections, reviewed Worker packages, version-specific permissions, revocation, and audit records.
Next
We plan to add guided LMS setup and a shared course app launcher, with clearer connection status. We also need to test Photo Roster in real Canvas, Moodle, and Brightspace courses.
Before using Lantern with real courses, your institution must review its accessibility, privacy, and security.
Bring a useful app to your campus.
Start with Photo Roster, or tell us about a course task your LMS could handle better.
Email info@longsight.com. The link opens your email app.