I have a client who is seeing our tool as an external link rather than an external learning tool?

Deanna.D.517
Deanna.D.517 Posts: 2 🔍
edited June 11 in Development

We are a partner of D2L (our company's name is Qwickly) and I have a client who is attempting to install Qwickly Jot into their Brightspace environment. We have a well-documented installation guide for this that we have checked with the client and, although they are following the steps exactly, when they add the tool as an external learning tool, it shows up in their courses as an external link instead (which does not work and results in an error). I've included screenshots below. Can someone please help me understand what might be happening here?

Screenshot 2025-06-02 at 9.21.19 AM.png Screenshot 2025-06-02 at 9.21.28 AM.png
Tagged:
· Share on Twitter

Answers

  • Karim.M.508
    Karim.M.508 Posts: 21

    Hello,

    The issue where Qwickly Jot shows up as a non-functional external link instead of a proper integrated external learning tool in Brightspace usually points to a configuration or setup detail during the LTI tool registration.

    Here are a few things to check or confirm with the client that commonly cause this behavior:

    1. LTI Tool URL & Launch URL:
      • Confirm that the exact launch URL they entered when adding the external tool matches your documentation precisely. Any typo or missing parameter can cause the tool to fail to launch properly and appear as a simple external link.
    2. Tool Configuration Type:
      • Ensure they selected the correct type of external tool (e.g., External Learning Tool or LTI Tool) in Brightspace. If they accidentally add it as a simple URL link instead of an LTI launch URL, it will behave like an external link.
    3. Tool Settings & Parameters:
      • Check if any custom parameters or key/secret pairs required for Qwickly Jot are correctly set. Missing or incorrect OAuth credentials often cause launch failures.
    4. Placement in the Course:
      • Confirm how they add the tool to the course. Sometimes, adding the tool in a module or content area incorrectly can lead Brightspace to treat it as an external link.
    5. Brightspace Version Compatibility:
      • Verify the client’s Brightspace environment is compatible with the Qwickly Jot version you provide. Occasionally, older LMS versions handle LTI tools differently.
    6. Browser Console & Network:
      • Sometimes, inspecting the browser developer console on the client’s side while trying to launch the tool can reveal CORS issues or failed requests.

    If not, please submit a support ticket for further investigation.

    Thanks.

    · Share on Twitter

Categories