Canvas

This guide shows you how to tell whether Canvas is available in a Space, and what to do when it is not.

This guide shows you how to promote a literal node on a Canvas into a first-class Schema or Experience.

This guide shows you how to bring a file onto a Canvas and turn it into structured content.

This guide shows you how generated content on a Canvas is accepted, and what you can and cannot do with it.

Canvas is the admin-only, versioned authoring surface for a Space. This section documents its snapshot format, its operations, and its access rules.

Canvas access requires both of these conditions:

Conversion turns a literal node — a definition held only as an artifact — into a first-class Schema, Experience, or Flow, and replaces the literal node with a reference node.

Canvas actions are available in the Studio Canvas editor. They are not part of the public REST API or the ligantic CLI. Access rules are in Canvas Access.

A flow:literal node holds a Flow definition. Running the node starts a run of that Flow.

Ingestion turns an uploaded file into an artifact on a Canvas. It is the only way external content enters a Canvas.

A Canvas is a named authoring surface in a Space. Each saved change to its content is kept as a version. Versions are not edited or deleted.

Content produced by table extraction and Schema derivation is accepted automatically when it is created. Users cannot review, accept, reject, supersede, edit, or re-run it in Studio or through the API.

A Canvas snapshot is the complete shared state of a Canvas at one version. Per-user client state, such as selection and the camera, is not part of it.

Canvas data is included in Space export and import, whether or not Canvas is available in the Space.

Tabular operations read the content of a Canvas node and produce previews, extracted tables, and Schema literals.