How to Use Generated Content on a Canvas

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

Prerequisites

Canvas must be available in your Space. See How to Check Whether Canvas Is Available in a Space.

What Happens to Generated Content

Table extraction and Schema derivation accept their output automatically. By the time the node appears on your Canvas, its content is already accepted.

Acceptance and Canvas History

Acceptance is not part of Canvas version history. Restoring an earlier Canvas version does not undo an acceptance.

What This Means for Conversion

Converting a Schema or Experience literal requires its content to be accepted. Because extraction and derivation accept automatically, a derived Schema literal converts without further action. See How to Convert a Canvas Literal Into a Resource.

Limitations

There is no review step. You cannot accept, reject, edit, or re-run generated content from Studio or the API, and the Canvas editor has no review control.

Canvas Conversion

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 Lifecycle and Versions

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.

Canvas Review and Provenance

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.