In Brightspace, a Mindjoy deployment is attached to a set of org units. If it was attached to your whole organisation, or to a department with all descendants included, Mindjoy shows up for every instructor below that point, including in courses that are not part of your rollout.
If you are running a pilot, or phasing Mindjoy in one faculty at a time, you can attach the deployment to just the course offerings that are actually using it. This guide shows how.
Before you start
Brightspace administrator access
Mindjoy already connected to Brightspace (see Connecting Brightspace (D2L) with LTI 1.3)
A list of every course offering that should have Mindjoy, including any course that already has Mindjoy content in it
The Deployment ID currently registered in Mindjoy, under Organization > Integrations
Use one deployment, then narrow it
Your Mindjoy organization holds one LTI registration, made up of one issuer, one client ID and one deployment ID. Mindjoy matches every incoming launch against those three values.
Creating a second deployment for a different set of courses will not work, because only one deployment ID can be registered in Mindjoy. Launches from the other deployment will be rejected.
So keep the one deployment you already have and change which org units it covers.
How Brightspace decides where Mindjoy appears
A course sees Mindjoy if it is one of the deployment's org units, or if it sits below an org unit that was added with descendants included.
Links follow the same rule. Navbar links and deep links are attached to org units too, so a navbar link added at organisation level appears in every course navbar regardless of how you scope the deployment.
Step 1: Narrow the deployment's org units
1. Click the Admin Tools (gear) icon and select Manage Extensibility
2. Open the LTI Advantage tab and find the Mindjoy tool
3. Click View Deployments and open the deployment whose Deployment ID is the one registered in Mindjoy
4. In the org units section, remove the entry for your whole organisation, or any department or semester added with descendants, if it covers courses that should not have Mindjoy
5. Click Add Org Units, search for each participating course offering, tick it, and click Add
Leave This org unit and all descendants unticked when you add a single course offering
Tick it only when every course below that department or semester should have Mindjoy
6. Save the deployment
Step 2: Check where your links live
Narrowing the deployment stops Mindjoy launching outside those org units, but a navbar link can still be visible. Tidy that up too.
Navbar links: go to Admin Tools > Navigation and Themes. If a Mindjoy link sits on the navbar used organisation-wide, remove it and add it only to the navbars used by participating courses.
Deep links and quicklinks: these are created under the deployment, so they inherit the org units you set in step 1. No extra work needed.
No navbar link at all: instructors can add Mindjoy inside course content as an External Learning Tool activity or a Mindjoy deep link. For a small pilot this is often tidier than a navbar link.
Watch out for courses that already use Mindjoy
Removing a course offering from the deployment applies to Mindjoy content that is already in that course. Those items stop launching. Check your full list of courses using Mindjoy before you remove anything.
Plan for new terms
Course offerings are usually recreated each term or semester. If you attach the deployment to individual course offerings, you will need to add the new offerings each term.
Attaching the deployment to a semester or department org unit with descendants included avoids that maintenance, at the cost of covering every course inside it. For a pilot, the per-course list is usually worth the extra step.
Check it worked
1. Open a participating course as an instructor, add an External Learning Tool activity or a Mindjoy deep link, and confirm Mindjoy appears
2. Open a course that is not in the deployment's org units and confirm Mindjoy is not offered
3. Launch Mindjoy from the participating course to confirm it still opens
Troubleshooting
Mindjoy is missing in a course that should have it
Confirm the course offering itself is in the deployment's org unit list, not just its parent department, and that the deployment you edited is the one registered in Mindjoy.
Mindjoy still shows in courses you removed
Check for a parent org unit that was added with descendants included. That covers the course even though you removed it individually.
The Mindjoy navbar link is still visible everywhere
Navbar links are managed separately from the deployment. Remove the link from the shared navbar under Admin Tools > Navigation and Themes.
Launch errors after creating a new deployment
A new deployment has a new Deployment ID. Copy it and update it in Mindjoy under Organization > Integrations.
Related articles
Connecting Brightspace (D2L) with LTI 1.3
How LTI works on Mindjoy
If you get stuck, email [email protected] with your Brightspace URL and the courses you are trying to scope to.