A Canvas integration is a piece of software that plugs an outside tool, such as a plagiarism checker, a video platform, or a grading assistant, directly into the Canvas learning management system so it behaves like a native part of the course. Instead of asking students and teachers to leave Canvas, log into a separate website, copy files back and forth, and then re-enter grades by hand, an integration brings that outside tool inside the assignment workflow they already use every day.
If you have ever clicked a button inside a Canvas assignment that opened a third party tool without a second login, you have used an integration. Most of them run on a behind-the-scenes standard called LTI, which is what makes the whole thing feel seamless. This guide explains what that standard does, how a typical integration is set up, and the habits that keep it working smoothly once it is live.
What an integration actually is
Under the hood, a Canvas integration is a controlled conversation between two systems. Canvas knows who the user is, which course they are in, and what assignment they opened. The external tool knows how to do one specific job well, whether that is checking a paper for plagiarism or hosting a video lecture. An integration is the agreement that lets these two systems share just enough information to cooperate without handing over everything.
The most common form this takes is called Learning Tools Interoperability, almost always shortened to LTI. LTI is an open standard, which means it is not owned by Canvas or by any single tool vendor. It is a shared set of rules, currently in version 1.3, that any compliant tool and any compliant learning management system can speak. Because it is a standard, the same plagiarism checker that integrates with Canvas can usually integrate with Blackboard, Moodle, or Schoology too, with only minor configuration differences.
That is the conceptual heart of it. An integration is not a plugin you install onto a server. It is a trusted handshake between Canvas and an external service, defined by a standard both sides agree to follow.
How the handshake works
When a teacher opens an integrated tool from inside a Canvas assignment, a quick sequence happens that students and instructors never see. It is worth understanding because almost every setup problem traces back to one of these steps.
First, Canvas launches the tool and sends along a small, signed package of information. This is the launch. The package answers a few questions the external tool needs: who is this person, are they a teacher or a student, which course and assignment are we in, and is this request genuinely coming from your Canvas instance. The signature is the important part. It is cryptographic proof that the request really came from your school's Canvas and was not forged by someone trying to sneak in.
Second, the external tool verifies that signature against keys it exchanged with Canvas during setup. If the keys match, the tool trusts the request and opens. If they do not match, the launch fails, which is exactly the behavior you want from a security standpoint.
Third, once the tool finishes its work, it can send results back to Canvas through what is called a service. A plagiarism checker, for example, can pass a similarity score and an originality report back into the SpeedGrader screen so the teacher never leaves Canvas to see them. Under LTI 1.3 these return trips are governed by named services, the most common being Assignment and Grade Services, which handles passing grades and scores back into the gradebook, and Names and Role Provisioning Services, which lets the tool see the course roster.
The whole exchange usually takes under a second, and the user experience is simply that a button worked. But that one button represents identity, permission, security, and data flow all negotiated automatically.
Setting one up, step by step
The exact screens differ by tool, but nearly every Canvas integration follows the same shape. At an institutional level a Canvas administrator does the heavy lifting once, and individual teachers then add the tool to their own assignments.
The administrator's part generally looks like this:
Get the configuration details from the tool vendor. For an LTI 1.3 tool this is usually a client ID and a configuration URL, or a JSON file describing the tool.
Register the tool as a Developer Key in Canvas. In the Admin area, under Developer Keys, the administrator adds an LTI key using the details from step one. Canvas generates its own client ID in return.
Enable the key and set its scope. The administrator turns the key on and decides which courses or sub-accounts can use it. Many schools enable it account-wide so every teacher has access; others restrict it to a pilot group first.
Add the tool as an external app. Using the client ID, the tool is installed at the account or course level so it appears in menus and assignment settings.
Once that is done, a teacher's part is much shorter. When creating or editing an assignment, the teacher chooses the integrated tool as the submission type, often labeled as an external tool. They pick the specific tool from a list, confirm a few options such as whether scores should flow back automatically, and save. From then on, student submissions route through that tool without anyone thinking about the plumbing.
If you are integrating a plagiarism and AI writing detector specifically, the only extra decision is usually whether the originality report is visible to students, visible only to the teacher, or hidden until after the due date. That is a policy choice, not a technical one, and it is worth making deliberately.
Best practices that keep it reliable
An integration that is set up carelessly will technically work and then quietly cause headaches for a semester. A few habits prevent almost all of them.
Pilot before you go school-wide. Enable the tool in one or two willing teachers' courses first, run real assignments through it, and confirm scores land in the gradebook correctly. A two week pilot surfaces problems while they are cheap to fix.
Match permissions to need. LTI tools request access to specific data, such as the roster or the gradebook. Grant what the tool actually uses and nothing more. If a plagiarism checker only needs to read submissions and write back scores, it does not need broad account access.
Decide the student visibility policy on purpose. Whether students see their own originality reports changes how they use the tool. Showing reports can teach students to self-correct citations before the deadline; hiding them keeps the focus on a final check. Neither is wrong, but the choice should be intentional and communicated.
Write down who owns the integration. When a key expires or a launch starts failing, someone needs to know it is their job to fix it. Name that person before you need them.
Watch for expiring keys and version changes. LTI 1.1, the older version, is being retired across the ecosystem in favor of the more secure 1.3. If your tool still uses 1.1, plan the upgrade rather than waiting for it to stop working.
Test the failure case. Submit as a student in a test course and confirm what happens when something goes wrong. A clear error is fine; a silent failure where a paper never gets checked is the dangerous one.
Common misconceptions
A few beliefs about integrations cause more confusion than the technology itself.
"An integration means the tool can see everything in my Canvas." It cannot. LTI is built around limited, declared scopes. A tool sees only the data it was granted, and the launch tells it only about the current course and user, not your entire institution.
"If the button doesn't work, the tool is broken." Far more often the problem is a configuration mismatch: an expired key, a wrong client ID, or a scope that was never enabled. The tool and Canvas are usually fine; their handshake just was not set up cleanly.
"Once it's integrated, students can bypass it." With the assignment configured to route submissions through the external tool, students cannot opt out of the check while still submitting normally. The routing is enforced at the assignment level, not left to student choice.
"Every integration needs IT to install software." Modern LTI integrations install no software on your servers. They are a registration and a trusted link, which is why a teacher can often add an approved tool to an assignment in under a minute.
The short version
A Canvas integration is a trusted, standards-based handshake that lets an outside tool work inside your courses without extra logins or manual data shuffling. The standard doing the work is LTI, the setup is a one-time administrator task followed by a quick per-assignment choice, and the difference between a smooth integration and a frustrating one comes down to piloting, permissions, and knowing who owns it. Get those right and the technology disappears, which is exactly what a good integration is supposed to do.