> For the complete documentation index, see [llms.txt](https://academy.synap.ac/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.synap.ac/doc/integrations/blackboard-lms.md).

# Blackboard LMS

Synap has an integration with Blackboard Learning Management System, read this guide to learn how to configure it.

Synap integrates with Blackboard through [**LTI 1.3 / Advantage**](/doc/integrations/lti/lti1.3-advantage.md). It allows students to launch Synap exams, courses and practice tests from their Blackboard courses without a separate sign-in. Results can be configured to be passed back to Gradebook.

{% hint style="info" %}
This integration is available to Enterprise customers. Contact your account manager if you need help with setup.
{% endhint %}

The integration supports:

* Launching Synap Exams and Collections from Blackboard.
* Instructor deep linking through Blackboard Content Market.
* Score passback to Blackboard when grade service access is enabled.

### Get started

1. View the [Synap listing in the Blackboard App Catalog](https://appcatalog.blackboard.com/details/synap).
2. Register Synap as an LTI 1.3 tool in Blackboard.
3. Complete the [LTI 1.3 / Advantage configuration](/doc/integrations/lti/lti1.3-advantage.md).

After configuration, instructors can open **Content Market** in a Blackboard course. Select **Synap Collection** or **Synap Exam** to add Synap content.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://academy.synap.ac/doc/integrations/blackboard-lms.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.