> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mesolab.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# MESO Canvas

> The editor where you revise unit plans, lessons and assessments.

**MESO Canvas** is the editor. Unit plans, lesson plans and assessments open in
it, and everything MESO generates is editable — it drafts, you revise.

> [!NOTE]
>
> Canvas is the **editor**. [MESO Assist](https://docs.mesolab.ai/teachers/assist.md) is the **chat**. They
> are different products and are easily confused. If you are editing a document,
> that is Canvas.

## Editing

Rewrite anything. Your edits are what persist — MESO does not silently overwrite
your work.

## AI actions

Alongside editing by hand, Canvas offers five actions that work on the document
you are in:

| Action | What it does |
| - | - |
| **Generate Objectives** | Drafts learning objectives from the surrounding context |
| **Suggest Activities** | Proposes classroom activities |
| **Enhance Outcomes** | Reworks the learning outcomes |
| **Create Rubric** | Builds a marking grid — see [Rubrics](https://docs.mesolab.ai/teachers/rubrics.md) |
| **Generate Questions** | Drafts questions |

These are the five. They work from the unit's context rather than from a text
selection, so they produce something coherent with the plan around them.

## Comments

You can leave comments on a document, and comments **thread** — a reply attaches
to the comment it answers rather than piling up separately. A thread can be
marked **resolved** once it has been dealt with.

Comments are per-user: they are yours, on your document.

## The context panel

Canvas shows what the document is connected to — its linked items and any
artifacts generated alongside it — so you can see how a lesson relates to its
unit without leaving the editor.

> [!TIP]
>
> Canvas is where the real work happens. A generated plan is a starting position;
> the version you actually teach from is the one you have edited. Expect to
> rewrite the timings, the examples and the pitch — those are the parts MESO
> cannot know.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.