Educators should be able to use the course access they already have.

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.

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.

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 record shows how important recurring subscriptions are to the business model.

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 help, and institutions still carry this integration work.

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.

Course access should be practical for educators and careful with student information.

Morrow gives your assistant course tools and guidance for using them.

Morrow connects the assistant you choose to your courses and gives it guidance shaped around the work of teaching.

The goal is to make the course access you already have useful. Choose the courses, name the task, review the evidence, and decide what happens next. Morrow works within the connected account’s permissions and your institution’s rules.

Morrow gives your assistant the knowledge to build Canvas New Quizzes and Item Banks, audit accessibility, map outcomes, compare sections, plan course content, review assessments, and carry approved changes across the courses you choose. Explore the course tools and see how Muse works.

The built-in guidance asks your assistant to connect learning goals with practice and assessment, follow the path a student takes through a course, and distinguish course evidence from a suggestion. It also guides the assistant to preserve the course’s design and check what the learning platform saved. Morrow includes course-audit guidance, course-work principles, and reference files in its package.

Morrow keeps reading and changing separate. Morrow and Canvas in Muse begin in Plan, where proposed changes wait for your review. Edit is an explicit choice. After a supported change, Morrow reads the item again and reports what the platform saved or needs you to check.

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 several 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 and guidance. You and your chosen assistant make sense of the evidence and decide what to do.

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.

Choose an assistant that meets your budget, privacy needs, and school rules. Morrow itself places no proprietary license between you and the course access you already have.

Keep student privacy part of course work.

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 uses the course access you already have. You choose the courses, and Plan shows proposed changes before they are saved. Morrow and Canvas in Muse keep Edit as a separate choice. The product shows failed checks and uncertain results for you to review.

Morrow uses the course roster to replace known student identifiers in supported records with labels such as Student A1. Each keeps its label map on the computer running Morrow. Read the Privacy Policy for the exact scope and limits.

Course material can still identify a learner through details in a discussion, submission, message, file, or other free text. Follow your institution’s rules and choose an assistant with suitable privacy terms and settings. Morrow’s privacy page explains the protection and its limits.

Clear privacy language names what Morrow protects, where protection ends, and which decisions remain yours.

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 while they 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 connects course work in Canvas and Moodle to the assistant educators choose. Blackboard support is in development. The person 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.