> ## Documentation Index
> Fetch the complete documentation index at: https://thehyperstack.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Other LMS (LTI 1.3)

> Issue credentials from any learning management system that supports LTI 1.3.

Any LMS that supports **LTI 1.3** can issue Hyperstack credentials. Canvas, Moodle, D2L Brightspace, Blackboard and Sakai have their own guides; use this one for the rest, and for self-hosted Canvas.

## Step 1: register Hyperstack in your LMS

In Hyperstack, click **Add integration**, then **Other LMS**, then **Integrate**.

**If your LMS supports LTI Dynamic Registration**: copy the **Registration URL** and paste it where your LMS registers LTI Advantage tools. It works for 7 days and connects the LMS to your organization only.

**If not, register by hand**:

1. Paste Hyperstack's values into your LMS:

   | Hyperstack value | Also called |
   | - | - |
   | Login URL | OIDC login or initiation URL |
   | Redirect URL | Redirect URI |
   | Launch URL | Target link URI |
   | Deep linking URL | Content selection URL |
   | JWKS URL | Public keyset URL |
   | Domain | Tool domain |

2. Allow the tool to receive names and emails.

3. Enter what your LMS shows in the Hyperstack form: **Issuer** (platform ID), **Client ID**, **Deployment ID** (optional), **Authentication request URL**, **Access token URL** (optional) and **JWKS URL**. Click **Save registration**.

![The Set up Other LMS page in Hyperstack with the registration URL, our values and the manual form](https://mintcdn.com/hyperstack/22bf_uXgnFdMeQAd/images/other-lms-setup.webp?fit=max\&auto=format\&n=22bf_uXgnFdMeQAd\&q=85\&s=a6a1b5bc93fee908fcc53ab64f83e0af)

## Step 2: add Hyperstack to a course

Teachers add Hyperstack from the LMS's content or external tool picker, choose a credential group, and place it where learners finish.

## Who gets a credential

| Role in the course | Sees | Gets a credential |
| - | - | - |
| Learner / student | Their credential | Yes, once per credential group |
| Teacher, course designer, LMS admin | The page to pick or change the credential group | No |
| Teaching assistant, observer, parent, guest | "Nothing to issue" | No |

Test with a student account (or your LMS's "act as user"). Teacher and admin accounts never get a credential, and preview modes such as Canvas **Student View** have no real email.

## What learners see

* **Well done**: their credential is ready, with **View my credential**. It is published at once and emailed to them. Opening the item again shows the same credential, never a second one.
* **Email address needed**: the LMS didn't share their email, so nothing was issued. Ask your LMS admin to share names and emails with Hyperstack.
* **Not set up yet**: the item isn't linked to a credential group. A teacher opens it and picks one.

## Troubleshooting

Every launch is on the **Logs** tab of the setup page in Hyperstack for 90 days, with what happened and why.

| What you see | Why | What to do |
| - | - | - |
| "Hyperstack is not set up for this LMS yet" | The LMS isn't registered in Hyperstack, or the registration is switched off | Finish the setup above, and check **Registrations** on the setup page |
| "Connect this LMS to Hyperstack" | The install isn't connected to your organization yet | An LMS admin types a connection code from the setup page (codes last 30 minutes) |
| "Open Hyperstack in a new window" | The browser blocks sign-in inside the course page (often Safari) | Click the button. It works in a window of its own |
| "This sign-in expired or was already used" | The page was open too long, or reloaded | Open the item again from the course |
| "Email address needed" | Names and emails aren't shared with Hyperstack | Turn on sharing in your LMS (see the steps above) |
| A learner got a credential too early | The item wasn't locked | Use your LMS's completion rules so the item opens only when the course is done |
| "Already connected to another Hyperstack organization" | That LMS key or site is linked to another organization | Contact Hyperstack support |

## Data and privacy

| | |
| - | - |
| Standard | 1EdTech LTI 1.3 Core and Deep Linking 2.0, OIDC login, RS256-signed messages. Our public keys: `https://api.thehyperstack.com/v1/lti/1.3/jwks` |
| Received on each launch | The LMS user ID, name, email, course roles, course ID and title, item ID and title |
| Stored | Name and email on the credential issued, the LMS and item it came from, and a launch log for 90 days |
| Not requested | Grades, rosters, submissions or other course content. Hyperstack asks for no LTI Advantage service access |
| Cookies | One sign-in cookie for 10 minutes on `api.thehyperstack.com`, or the LMS's own storage when it offers it |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.