> ## 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. # Blackboard Integration > Issue a credential automatically when a learner reaches a Hyperstack item in Blackboard Learn. Hyperstack connects to Blackboard Learn (Ultra and Original) through **LTI 1.3**. A Blackboard admin registers Hyperstack with its Application ID; teachers then add a Hyperstack item to a course and choose a credential group. > [!NOTE] > > The Blackboard setup page in Hyperstack shows **Blackboard is coming soon** until Hyperstack's Blackboard listing is live. The steps below appear there as soon as it is. ## Before you start * A [credential group](https://thehyperstack.com/docs/tutorials/credential-setup/creating-credential-group.md) with its design. * Administrator access in Hyperstack. * A Blackboard system administrator. ## Step 1: register Hyperstack in Blackboard **1. In Hyperstack, open the Blackboard setup page** Click **Add integration**, then **Blackboard**, then **Integrate**. Copy the **Application ID**. **2. In Blackboard, go to Administrator Panel, LTI Tool Providers** Click **Register LTI 1.3/Advantage Tool**, paste the Application ID in **Client ID** and click **Submit**. **3. Approve the tool** Check **Tool Status** is **Approved**, and under **User Fields to Send** allow role, name and email. **4. Connect Blackboard to your organization** In Hyperstack, click **Make connection code**. Open a Hyperstack item once in Blackboard as an administrator and type the code when asked. Each Blackboard site needs its own code. ![The Set up Blackboard page in Hyperstack](https://mintcdn.com/hyperstack/22bf_uXgnFdMeQAd/images/blackboard-setup.webp?fit=max\&auto=format\&n=22bf_uXgnFdMeQAd\&q=85\&s=b31b46c98f9dea593cf2ba6ef50ce7cd) ## Step 2: add Hyperstack to a course 1. In the course, open **Content Market** (Ultra) or **Build Content** (Original) and choose **Hyperstack**. 2. Hyperstack shows your credential groups: choose one and click **Add to course**. 3. Use **release conditions** (Ultra) or **adaptive release** (Original) so the item opens only when the learner has finished the course. ## 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.