LTI 1.3 Setup New

Dr. Olivia can be added to a partner institution's Canvas as an LTI 1.3 (LTI Advantage) tool, so students and faculty launch her right from inside a Canvas course — no separate login page. This guide is for Canvas administrators and institutional IT at a partner school. (Existing PHSU users keep signing in exactly as they do today — nothing changes for them.)

Who does what Your Tiber contact provisions Dr. Olivia for your institution and gives you the URLs below. You create two Developer Keys in Canvas and share a few values back. The detailed operator runbook lives with the Tiber team.

How a Launch Works

A user clicks the Dr. Olivia link in a Canvas course.
Canvas securely confirms who they are and which institution they're from (LTI 1.3, signed).
Dr. Olivia then runs the normal Canvas sign-in to connect to that user's courses — the same Canvas authentication used everywhere else.
The user lands in Dr. Olivia, with everything (avatar, chat, materials, quizzes) working as usual.

Keeping the Canvas sign-in step is deliberate: it's what lets Dr. Olivia read the student's own course materials on their behalf.

What You'll Set Up in Canvas

You'll create two Developer Keys:

1. The LTI 1.3 Key (the launch)

Target Link URI — https://<tutor-host>/lti/launch
OpenID Connect Initiation URL — https://<tutor-host>/lti/login
Public JWK URL — https://<tutor-host>/lti/jwks.json
Redirect URI — https://<tutor-host>/lti/launch
Custom field (required) — canvas_user_id=$Canvas.user.id
Placement — add it where you want the link (e.g. Course Navigation) and set it to open in a new tab/window.

Open in a new window The Canvas sign-in step can't run inside the small course iframe, so the placement must open Dr. Olivia in a new tab/window. If you skip this, the launch will appear to stall.

2. The API Key (the Canvas connection)

A standard Canvas API Developer Key so Dr. Olivia can read the signed-in user's courses. Redirect URI: https://<tutor-host>/auth/<your-partner-code>/code. Share its Client ID and secret with your Tiber contact (they're stored encrypted).

What to Send Back to Tiber

The LTI key's Client ID and Deployment ID.
Your Canvas issuer and the platform auth / token / JWKS URLs (standard Canvas values).
The API key's Client ID and secret, and (optionally) an admin API token if you want students auto-enrolled into a Virtual Tutor course.
The list of faculty (name + email) who should get the faculty experience — everyone else launches as a student.

Roles: Students vs. Faculty

For partner institutions, faculty are identified by an explicit list you provide (name + email). Anyone who launches and isn't on that list is treated as a student. Let your Tiber contact know when the faculty list changes.

Troubleshooting

Symptom	What's likely happening
"This institution is not configured for Dr. Olivia LTI access."	The Client ID / Deployment ID / issuer don't match what Tiber has on file. Re-check the values from your LTI key.
"This tool requires the canvas_user_id custom field."	The custom field `canvas_user_id=$Canvas.user.id` wasn't added to the placement.
The launch opens but never gets past a blank/login screen.	The placement isn't set to open in a new tab/window, so the Canvas sign-in is trapped in the course iframe.
A faculty member shows up as a student.	Their email isn't on the faculty list, or doesn't match their Canvas email. Send the corrected list to Tiber.