# Canvas field labels

**Version:** v2026-05-05

**Published:** May 11, 2026

## Field labels in Canvas

Field labels replace the previous content mapping approach with a direct, visible connection between what you write and where it goes in Studio.

When you set a content type on a Canvas document, field labels appear inline as purple headings that correspond to fields in your schema. You can see and adjust the structure of your document as you write, without switching to a separate panel.

### What changed

**Structure is now part of the document.** Content mapping previously lived in a side panel you had to open to check the state of your document. Field labels sit inline, so structure is visible as you write.

**Content-to-field assignment works differently.** The background AI process that continuously mapped content is gone. Field labels can be applied in two ways: manually using the `=` slash command, or automatically via AI labeling that you trigger when you’re ready. After AI labeling runs, you can always review and adjust the results.

**Inclusion replaces content/context toggling.** Instead of marking blocks as “content” or “context,” you now toggle individual blocks between “included in Studio” and “excluded” using an eye icon in the margin. Excluded blocks stay in the document and will not be sent to Studio. 

**Delivering to Studio is an explicit action.** Previously, connecting a Canvas document to Studio started a continuous sync. Now you first select a content type, then choose *“Create new Studio document”* or *“Update Studio document”* when you’re ready. Setting a content type alone doesn’t create anything in Studio.

**Studio documents are never locked.** Content mapping blocked Studio editing while a Canvas document was linked. With field labels, Studio documents can always be freely edited. When you push an update from Canvas, it flags any fields that have changed in Studio since your last update so you can review conflicts before overwriting.

### Applying field labels

Field labels can be applied to an entire document or a selected range. AI reads your content against the selected content type, sorts it according to the schema, and applies labels for you to review.

This is especially useful when bringing existing content into Canvas from tools like Google Docs or Notion and structuring it for Studio quickly.

For finer control, use the `=` slash command to assign a label to any block manually. You can also select text and pick “Label this content” from the context toolbar to label a specific section.

### Including and excluding content

Within any field label, toggle individual blocks between included and excluded using the eye icon. Only included content flows to Studio when you create or update a document.

Excluded blocks are useful for keeping editorial notes, content briefs, reviewer comments, or alternative drafts inline without cluttering the Studio document. You can draft multiple variations within a field label and toggle which one to include before sending to Studio.

### Sending to Studio

Open the content type panel and select “Create new Studio document” to send labeled content as a new draft. If your team uses Content Releases, you can create the document directly into an existing release.

Once created, the Studio document stays connected to the Canvas document. Continue refining in Canvas and push updates when ready. If fields have been edited in Studio since your last update, Canvas flags the conflicts before anything is overwritten.

### What stays the same

The writing experience (editor, formatting, slash commands, Markdown shortcuts), AI assistance (ghostwrite, show options, rewrite), notes (context, fact, style, inspiration), and real-time collaboration all remain unchanged. Field labels re-imagine how structure is surfaced and how content moves from Canvas to Studio.