Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Tool guide
Canvas
Defines source-aware Canvas LMS course, content, assessment, integration, permission, and data review, evidence handling, and action boundaries.
Read the fileOverview
Canvas overview
Use this bundle to prepare source-aware Canvas LMS course, content, assessment, integration, permission, and data review and a review-ready Canvas LMS change brief.
Read the fileWorkflow
Canvas source-aware triage
1. State the requested decision or artifact. 2. Inventory evidence: Canvas instance, environment, release, account, subaccount, course, term, section, and object IDs; user, role, enrollment.
Read the fileTemplate
Canvas LMS change brief
Review-ready artifact for Canvas LMS course, content, assessment, integration, permission, and data review, evidence quality, verification, and controlled actions.
Read the fileIs this bundle right for your task?
Who it is for
- People who configure, operate, integrate, govern, or review work performed in Canvas
- Teams working in Technology, Business operations
When to use it
- A proposed Canvas configuration or workflow change needs current IDs, permissions, dependencies, tests, and rollback evidence.
- A report, export, integration, or automation result needs to be reconciled against actual workspace state and current product documentation.
What you need to provide
- The product version or workspace scope, relevant configuration or export, desired outcome, permissions, and accountable owner.
- Current IDs, settings, records, logs, screenshots, integration details, and test evidence needed to verify the requested change.
Tasks and expected outputs
Questions it helps answer
- Prepare a Canvas LMS change brief without fabricating local facts.
- Separate verified, provided, assumed, and missing evidence.
- Produce a review-ready decision with explicit verification and approval boundaries.
What it helps produce
- Canvas LMS change brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the product version or workspace scope, relevant configuration or export, desired outcome, permissions, and accountable owner. Ask the agent to review Canvas and produce Canvas LMS change brief that maps configuration evidence, dependencies, permissions, tests, rollback, and actions that still require approval. Begin with instructure.com — Canvas, then confirm that the reference is current and applicable. Inspect Canvas before drafting.
Context path: bundles/tools/canvas-instructure
What the bundle includes
Tools
- Canvas
Frameworks
- source-evidence matrix
- Canvas LMS course, content, assessment, integration, permission, and data review matrix
- qualified-review gate
Evaluations
- Canvas source-awareness check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Changing live configuration, records, permissions, automations, integrations, or shared data without verified scope, testing, rollback, and approval.
Known limitations
- Use the listed authoritative sources for general role or tool behavior; local configuration, records, values, states, permissions, and results require inspected evidence.
- Task-specific work requires current evidence for Canvas instance, environment, release, account, subaccount, course, term, section, and object IDs; user, role, enrollment, permissions, OAuth scopes, developer key, LTI or SIS integration; content, module, assignment, rubric, quiz, dates, gradebook, files, accessibility, privacy, audit, backup, test, and approval evidence.
- Do not infer course state, permission, enrollment, grade, due date, content visibility, integration behavior, accessibility, or student outcome.
Safety notes
- Minimize personal, customer, employee, financial, credential, security, privileged, health, student, and other sensitive data.
- Require explicit confirmation before actions that publish or change course content, enroll users, alter grades or dates, send messages, import SIS data, install an integration, or access student records.
- Route legal, privacy, security, compliance, financial, employment, clinical, safety, and other qualified judgments to an evidenced accountable reviewer.