Student Authorship Verification for Canvas LMS: LTI 1.3 Setup and Buyer's Guide

For Canvas administrators and university teaching teams: Writing-process evidence can complement a normal Canvas assignment workflow, but only when instructors can reach the record, students understand when recording begins, and an administrator can operate the integration safely. An LTI tool should not add a new, opaque score to a misconduct investigation.

AuthMarks documents an LTI 1.3 integration for Canvas, with instructor-linked assignments, student access and sealed record links. Its published Canvas setup guide provides a tool configuration URL and a separate tenant-activation step. This article explains how to evaluate that integration with an institution's actual Canvas configuration.

Disclosure: AuthMarks publishes this page and provides the software described. This is not an independent compatibility certification, performance comparison or guarantee that every Canvas tenancy has been tested.

For the wider vendor landscape, see the student authorship verification software buyer's guide before assessing Canvas-specific integration.

What a university should expect from Canvas authorship verification

In an ordinary LMS workflow, a teacher creates an assignment, learners complete the writing, and the LMS records a submission. Authorship verification adds another question: What evidence exists of how the submitted text was developed?

A process-evidence tool may show observed typing, pasting, revisions and gaps, subject to supported editors and active recording. A sealed artifact may allow an authorized reviewer to check that the retained record has not been altered since sealing. Neither step, by itself, proves that a particular physical person typed every character or that a student violated a rule.

The expected workflow for AuthMarks, as described by its vendor documentation, is:

1. The Canvas instructor links an AuthMarks activity from the course.
2. A student uses a supported writing surface and enables recording for the relevant document.
3. The student reviews the writing record and completes named attestation before sealing.
4. A linked submission or record reference becomes available to the instructor within the LMS workflow.
5. An authorized reviewer examines the evidence, including any unobserved text, under the university's policies.

The university must test this exact path in its Canvas tenant. Do not equate a vendor's architecture diagram with a completed production acceptance test.

Why LTI 1.3 matters—and what it does not guarantee

Learning Tools Interoperability (LTI) 1.3 is a technical standard designed to support secure connections between a learning platform and an external tool. It is not itself an academic-integrity assessment method. The 1EdTech LTI overview describes security based on modern identity and authorization mechanisms.

LTI Advantage adds optional, separately defined capabilities:

Capability	General purpose	Question for procurement
Core LTI 1.3	Secure launch from the LMS to a registered tool	Can the right student and instructor launch successfully?
Deep Linking	Instructor selects and places tool content within a course	Can the instructor link an authorship-verification assignment without a manual URL?
Assignment and Grade Services	Exchange assignment/grade-related data when implemented	What exactly is sent to the gradebook: completion, link or a numerical grade?
Names and Role Provisioning	Controlled access to users, roles and memberships	Does the tool request the minimum data the university approves?

AuthMarks' public LTI page says grade passback is progress-only by default unless an institution opts into a numeric score. That is a vendor-published configuration statement that should be checked during the pilot. No institution should infer from a numeric passback capability that an academic misconduct verdict is generated.

Certification note: A tool that states it supports LTI 1.3 is not automatically certified by 1EdTech for LTI Advantage services. Request proof of current certification if your procurement standard requires it.

Canvas administrator setup: a documented starting path

The AuthMarks LTI documentation currently describes the following Canvas registration process:

1. In Canvas, an authorized administrator opens Admin → Developer Keys → + LTI Key.
2. Choose the URL-based configuration method and supply the public AuthMarks Canvas configuration URL: https://www.authmarks.com/api/lti/config/canvas.
3. Review the permissions, placements, redirects and data-sharing fields; do not blindly enable unnecessary access.
4. Enable the LTI key, then install/configure the app from Settings → Apps using the Client ID.
5. Provide the resulting Client ID and deployment ID to AuthMarks for tenant activation, using the vendor-approved communication channel.
6. Validate launch, assignment linking, submission reference, roles and failure handling inside a test course.

These are high-level, vendor-published setup steps—not credentials, a promise of automatic provisioning or an instruction to bypass your university's change-control process. Canvas menus and installation paths may change. Follow your institution's Canvas admin documentation and Instructure's current administrator guide for the interface available in your tenant.

LTI tool registration does not mean students need no writing-side software. AuthMarks' published institution workflow mentions a supported browser extension for recording in Google Docs and Word, alongside its own writing editor. Confirm the exact student deployment steps, supported operating systems, and accessibility requirements before rollout.

A five-minute functional test is not a complete pilot

An admin can confirm a login quickly, but a real academic assignment requires more. During pilot acceptance, ask the teaching team to demonstrate:

Test 1 — Instructor placement: A teacher can add the correct tool activity to the correct course, without exposing administrative controls.

Test 2 — Student launch: A student in the course can access the assignment with expected identity and role attributes. A student in another course cannot see private evidence they are not authorized to access.

Test 3 — Normal writing: A consenting test student writes and revises a document, attests and seals, then sends the expected link through the Canvas workflow.

Test 4 — Missing evidence: The student writes before recording begins or pauses recording. The reviewer sees a meaningful distinction between recorded and unobserved work, rather than a fabricated history.

Test 5 — Review boundary: The instructor can reach the record associated with their assignment but cannot browse unrelated student sessions or documents.

Test 6 — Failure case: Break the simulated launch or use an inactive deployment. Confirm the student receives an actionable message and support can distinguish LMS configuration from product-side problems.

Keep screenshots and timestamped notes for each test. Use synthetic assignments rather than real student misconduct investigations during integration acceptance.

Instructor workflow: explain evidence instead of scores

An effective instructor orientation might say:

The provenance record helps us understand what happened during a recorded writing session. Typed, pasted, suggested, automated and untracked regions are contextual information. A pasted quotation is not misconduct. An untracked section means we lack direct recording of that section. Any academic-integrity question will be reviewed using the institution's normal process and the student's explanation.

This avoids creating a parallel disciplinary system inside the LMS. If the institution permits AI assistance for brainstorming or editing, students should receive examples of acceptable and unacceptable use in the assignment instructions, not have to infer policy from software labels.

Canvas-specific procurement and privacy questions

Before purchase, ask:

• Which Canvas deployment environments and account/subaccount scopes have been tested?
• Is Canvas Apps marketplace distribution available, or is manual LTI registration required today? Do not assume a marketplace listing merely because LTI works.
• Which LTI service scopes and personal data claims does AuthMarks request, and why?
• Can the instructor view records without receiving grades or AI scores?
• Where do students perform capture: Google Docs, Word, AuthMarks editor, or an early-access component?
• What happens when recordings are off, rejected or interrupted?
• Can consent and evidence-sharing rules be adapted to local policy?
• How long is evidence retained; what is exportable; who can access it?
• What support and contract arrangements apply to an institution-wide deployment?

To prepare a consistent vendor RFP, use the authorship-verification procurement checklist.

How AuthMarks differs from an ordinary Canvas detector integration

A detector integration typically analyzes a completed artifact and returns some form of interpretation about the finished text. AuthMarks describes a process-recording and attestation workflow: recording with document-level consent, displaying observed and unobserved text, recording a named review and sealing the result for verification. This is a difference in method and evidence objective—not a measured claim that one product is more accurate than another.

A valid seal can show that the sealed artifact has not changed. It does not establish the physical identity of the typist or make an academic-misconduct decision. For those limitations, see AuthMarks' institution explanation.

Frequently asked questions

Can AuthMarks connect to Canvas through LTI 1.3?

The vendor's current integration page documents a Canvas LTI 1.3 setup path. Administrators must register the tool and coordinate tenant activation; test the resulting configuration in your own tenant.

Is AuthMarks listed in the Canvas marketplace?

This article does not claim a marketplace listing. Marketplace approval and LTI interoperability are distinct questions. Check the current marketplace and obtain the vendor's listing reference if marketplace procurement is mandatory.

Does Canvas automatically mark an assignment as AI-written?

AuthMarks' published approach is not an AI-detector score. The gradebook integration should be tested for exactly which link, status or grade data it sends, rather than assuming that it reports cheating.

Can students refuse recording?

AuthMarks describes document-level consent and the ability to stop recording. Institution policy, local law and accessibility requirements determine how a particular course should handle non-participation or alternative evidence.

What does it cost for Canvas institutions?

The public pricing page lists institutional quotations based on scope, not a universal Canvas tariff. See the total-cost guide or ask for an institution-specific quote.

Evaluate AuthMarks in your Canvas environment

For a pilot, email sales@authmarks.com with your Canvas deployment scope, number of courses, expected student volume, required writing environments and evidence-retention needs. Ask for a validated implementation scope—not only a demonstration video.

Explore: AuthMarks for institutions · LTI setup documentation · 30-day university pilot playbook

Related: Authorship verification software buyer's guide · Blackboard integration guide · Procurement checklist · Pricing guide