01
The information is already there.
Assignments, submissions, discussions, rubrics, grades, modules, outcomes, and course materials already hold evidence about what people were asked to learn and where the learning experience may need attention.
Yet access is not the same as use. That information is often scattered across pages, reports, sections, menus, and separate products. An instructor may be authorized to see every part of it and still have no practical way to ask a question across all of it. An instructional designer may be responsible for twenty courses and still have to inspect the same pattern twenty times. A program team may know that a problem exists but lack a safe, direct way to find where it repeats.
Learning platforms already know which assignments belong to which modules. They hold instructions, due dates, discussions, submissions, feedback, and scores. They also apply roles and permissions that decide what each signed-in person may see or change. Official Canvas documentation shows this permission model in its rules for user approval, limited scopes, and administrator enablement.[1]
The platform can show each piece. Teaching often needs the relationship among the pieces. An instructor may want to compare how students performed on one concept across four sections, then inspect the related instructions, rubric criteria, and discussion activity. A curriculum developer may want to trace one outcome through a whole program. A quality team may need to find the same accessibility barrier across hundreds of pages.
These are reasonable questions about information the institution already holds and the educator may already be allowed to use. The difficulty lies in joining the pieces. Morrow begins with a simple conviction: people should be able to make responsible use of the course information they are already trusted to see.
If an educator is trusted to see the course, that educator should have a safe way to ask useful questions of it.
02
A useful assistant should not begin with a second gate.
The first gate is legitimate authorization. The second gate is commercial.
A person should reach only the courses and information allowed by that person’s role. This boundary protects learners and institutions. It should remain in force.
But even after a person has legitimate access, modern ways to use that information can depend on whether the institution buys another product, approves another agreement, enables another feature, or assigns technical staff to another integration. Instructure’s current Canvas tiers place some assistant and analytics features in higher product levels that require an institutional quote.[2] Instructure has also said that continued access to premium IgniteAI features after a preview period requires Canvas Plus or Canvas Next.[3]
This creates an uneven result. An educator at a well-funded institution may receive a capable tool. Another educator doing the same work may receive nothing. A small program may wait through a procurement cycle. An adjunct may have no voice in the decision. An instructional designer may use a capable assistant with documents, then lose that capability at the exact point where the work reaches the LMS.
The burden does not disappear. People do the work by hand. They copy information into spreadsheets, repeat the same search in many courses, or make decisions from a partial view because a complete view takes too long to assemble. A federal education toolkit describes educators creating their own systems, preparing information on their own time, and waiting through difficult access and analysis processes.[6]
Useful teaching tools should not depend entirely on institution-wide purchasing power. A person’s authorized access should be more than permission to click through screens one at a time. It should support the questions that person is responsible for answering.
03
Why fragmented systems remain profitable.
We believe vendors can profit when educators need extra products or services to use information already stored in their course systems.
We should be precise about that belief. We cannot know the private motive behind every product decision. Companies face real engineering costs, security duties, support needs, and legal obligations. Earning money from a useful product is not itself a problem.
The problem is an incentive that rewards fragmentation. When course information remains difficult to combine, each connection can become a separate product. When interfaces remain obscure, practical access can become a specialist service. When assistant features are tied to enterprise agreements, a way of working that already exists elsewhere becomes another item for institutional procurement.
The business model is visible. In its 2023 annual report, Instructure said subscription and support produced 92 percent of its revenue. It also described annual or multi-year contracts and growth through wider use by existing customers.[4] That historical record proves a recurring subscription model. It does not prove a hidden intent to obstruct educators.
The friction is visible too. 1EdTech’s procurement guidance says fragmented credentials, custom files, and grade transfer can be time-consuming and error-prone. It says integrations strain institutional technology teams and often need custom development.[5] Open standards exist because this problem is real. The continued burden shows that a standard on paper does not always become simple access in practice.
Whatever its original cause, fragmentation now has economic value. A platform can publish interfaces while complete use still depends on administrator settings, specialist knowledge, and custom work. A product can call itself integrated while keeping the institution and educator dependent on one vendor’s roadmap.
We do not accept this distance as inevitable. Complexity should protect people from harm. It should not create an unnecessary fee for access.
04
Morrow gives your assistant practical course tools across the LMS.
Morrow connects the assistant a person chooses to the courses that person can already open.
The goal is to make existing authority useful. A person chooses the courses, names the task, reviews the evidence, and decides what happens next. Morrow does not turn an instructor into an administrator. It does not open a course that the signed-in account cannot reach. It does not work around institutional policy or a platform’s refusal.
Morrow gives your assistant practical course tools across the LMS. It can plan and create approved course content, review assessments, build and reshape New Quizzes and the Item Banks behind them, audit course content for accessibility issues, map curriculum and accreditation evidence, compare sections, and carry approved changes across many courses. For Canvas and Moodle, the course sign-in stays in Chrome. For Blackboard, an administrator connects Morrow to the school first. In every case, the existing account and its permissions set the limit.
Morrow also keeps reading and changing separate. Every selected course begins in Plan. Proposed changes wait for review there. A person can grant Edit access only to selected courses and selected kinds of change. After a change, the assistant uses Morrow to read the item again and report what the platform saved, what it skipped, and what it could not confirm.
Use these tools for one course question, a course-content plan, a selected New Quiz change or Item Bank review, an accreditation review, an accessibility repair plan, or coordinated work across many courses. The assistant can continue in the same conversation and prepare a chart, faculty brief, lesson, assessment, or message draft. Morrow supplies the course tools. The chosen assistant does the thinking and writing with the person.
Morrow is and always will be free and open source. That is a product decision and a statement about power. People can inspect the connection, question its choices, test its behavior, and propose improvements. Institutions can inspect how Morrow works instead of relying only on sales language. Educators have an alternative when a bundled tool does not fit their work.
Open source does not remove every cost or rule. A chosen assistant may have its own price, terms, and privacy settings. An institution may control browsers, networks, or approved software. Morrow makes a durable promise: it will not place its own proprietary license between an educator and the course access that educator already has.
05
Ten Principles for Useful Access.
These principles turn the philosophy into choices that people can inspect.
- 01
Authorized access should be useful access.
If a person is trusted to use course information, that person should have practical tools for understanding it and acting within the same authority.
- 02
Educators should ask their own questions.
A fixed dashboard cannot anticipate every course, discipline, learner group, or teaching decision. The person closest to the work should be able to name the question.
- 03
Existing authorization must remain in force.
Morrow should never expand a person’s LMS role, evade an institution’s controls, or treat system access as permission.
- 04
Privacy must shape the connection.
Access should stay limited to the courses the person selects and the information the task requires. Privacy claims must state their limits.
- 05
Human review is part of the method.
Assistants can examine, prepare, and recommend. Educators interpret, approve, revise, and remain responsible for the result.
- 06
Evidence should support better teaching.
The purpose of analysis is a clearer decision, a stronger course, more useful support, or a better learning experience.
- 07
The saved result must be checked.
A successful request is not enough. After a change, the assistant uses Morrow to read the course again and report what the platform actually saved.
- 08
Uncertainty should remain visible.
A tool should say when it lacks evidence, when a result could not be confirmed, and when a person needs to inspect the course directly.
- 09
Educators should keep their choice of tools.
No single assistant, vendor, or institution-wide purchase should define every educator’s access to modern ways of working.
- 10
Course connections should stay open.
People should be able to inspect and improve the connection between authorized course information and the tools they use.
06
Convenience cannot come at a learner’s expense.
Course access can include names, grades, submissions, messages, and personal details. That makes privacy a core design duty.
A useful assistant may need enough context to separate missing work from low scores, compare activity across sections, or prepare support for a specific learner. The same access can create harm if too much information reaches an assistant, if a request uses the wrong course, or if a proposed action is saved without the intended boundary.
Federal guidance for online educational services calls for limits on collection and use, direct institutional control, defined access, retention and deletion rules, and safeguards for disclosure.[8] UNESCO’s guidance for generative tools in education calls for privacy, human agency, and both ethical and pedagogical validation.[9]
Morrow limits access. The person connects a signed-in course and chooses which courses Morrow may use. The LMS sign-in remains in the browser. Read access and Edit access are separate. The product shows limits and failed checks instead of turning an uncertain result into a confident claim.
Morrow first confirms the course and builds a complete identity list for the records it will read. It replaces known student identifiers in those records with labels such as Student A1 before it sends the records to your assistant. For an approved course action, Morrow matches each label back to the student only on this computer and in the selected course. If it cannot identify and protect every student in those records, it stops.
It does not make every piece of course content anonymous. A learner may include identifying details in a discussion, submission, message, file, or other free text. The educator must still follow institutional rules and choose an assistant with suitable privacy terms and settings. Morrow’s privacy page explains the current behavior and its limits.
Privacy language should tell people what the product does, what it cannot guarantee, and which decisions remain theirs. Trust grows from clear limits. It does not grow from an absolute promise that the product cannot keep.
Evidence should sharpen an educator’s judgment. It should never replace it.
07
Evidence should reach the people who teach.
Course information has little value when it ends as another report that no one has time to interpret.
Evidence matters when it changes a decision. A pattern of missing work may lead an instructor to revise pacing. Repeated confusion around one rubric criterion may reveal unclear instructions. A comparison across sections may show that one learning activity needs more preparation. A curriculum map may expose an outcome that is assessed but never practiced. An accessibility review may find one barrier that repeats across many pages.
The U.S. Institute of Education Sciences recommends an ongoing cycle in which educators collect and prepare evidence, interpret it, form a hypothesis, change instruction, and return to the result.[7] Morrow helps educators move through this cycle more quickly. It does not decide what good teaching requires.
An assistant can examine more material than a person can inspect in one sitting. It can find patterns, prepare comparisons, draft revisions, and organize possible next steps. It cannot know every part of a classroom. It may not know why an instructor granted an extension, how a cohort experienced a difficult week, which accommodation applies, or what a learner chose to share in confidence. It can make a confident mistake.
Human review is therefore part of the method. Morrow should help an educator inspect the source behind a recommendation, keep boundaries visible, and distinguish a confirmed result from an uncertain one. The educator still decides what the evidence means, whether a proposed change belongs, and what a learner needs.
Open tools can make that capability more equal. UNICEF describes digital public goods as open software, information, models, standards, and content that can be reused and scaled to advance equity.[10] Morrow follows the same open model. People can inspect, share, and adapt it without waiting for a company to decide that their need is profitable.
Morrow does not exist to replace Canvas, Moodle, Blackboard, an institution’s policies, or an educator’s judgment. It exists to connect what is already there. The person chooses the assistant, chooses the courses, asks the question, reviews the evidence, and decides what happens next.
The silos may be profitable. They are still a design choice. Morrow is our proof that we can choose a careful, private, open bridge instead.
Notes
Sources and Further Reading
The argument separates published facts from Morrow’s point of view. These primary sources support the facts above.
- 01
Instructure, Canvas Developer KeysOfficial rules for user approval, limited access scopes, and administrator enablement.
- 02
Instructure, Canvas Product TiersCurrent placement of analytics and assistant features in Canvas Plus and Canvas Next, with institutional quote-based pricing.
- 03
Instructure Community, IgniteAI Access ExtensionInstructure’s statement that premium access after 31 July 2026 requires Canvas Plus or Canvas Next.
- 04
Instructure Holdings, 2023 Form 10-KHistorical evidence for subscription and support revenue, contract terms, and expansion within existing customers.
- 05
1EdTech, OneRoster Planning and Procurement GuideDocumented integration burden from fragmented sign-ins, custom files, grade transfer, and custom development.
- 06
Regional Educational Laboratory Northeast and Islands, Building a Culture of Data UseExamples of educators building local systems and spending time preparing information because access and analysis are difficult.
- 07
Institute of Education Sciences, Using Student Achievement Data to Support Instructional Decision MakingEvidence as an ongoing cycle of interpretation, action, and review.
- 08
U.S. Department of Education, Protecting Student Privacy While Using Online Educational ServicesGuidance on purpose limits, control, access, retention, deletion, and disclosure safeguards.
- 09
UNESCO, Guidance for Generative AI in Education and ResearchGuidance on privacy, human agency, ethical validation, and pedagogical validation.
- 10
UNICEF, Digital Public GoodsSupport for open resources that can be reused and scaled to advance equity.