The Schema editor defines the structure of entries for a tag. It controls which fields appear when creating entries, how those fields are arranged, and which schema version is active.

Entries use the active schema. Schema changes are saved as a draft first, so you can review the structure before publishing it for new entries.

Schema states

• Active schema means entries can be created from the published field structure.
• Active with draft means existing and new entries still use the active schema until the draft is published.
• Draft only means a schema draft exists, but it must be published before entries can use it.
• No schema means the tag needs a schema before entries can be created.

Schema fields

• Add fields when entries need to collect more information.
• Open field settings to edit the label, key, type, required state, overview visibility, and type-specific configuration.
• Each field is shown as a disabled preview block so you can see how the entry form will feel without entering real entry values.
• Required fields must be filled in when creating or editing entries.
• Fields marked as shown in overview can appear in entry list and tile previews.

Field types

• Text fields are useful for notes, descriptions, names, instructions, or longer written values.
• Number, date, and yes/no fields are useful for structured values that should be entered consistently.
• Link fields store URLs or references to external resources.
• Image fields allow entries to include photos or visual documentation.
• Label and icon fields help structure the entry form or visually separate sections.

Layout editing

• Fields are arranged on a layout grid, similar to profile blocks.
• Moving a field changes where it appears in the entry form layout.
• Resizing a field changes how much space it gets in the form.
• The breakpoint selector lets you preview and adjust the layout for desktop, tablet, and phone widths.
• Undo and redo let you step through layout changes while arranging fields.
• If fields overlap in the current layout, the editor highlights the problem and prevents saving until the layout is valid.

Draft workflow

• Save Draft stores schema changes without immediately making them active for entries.
• Publish Draft makes the draft schema active so new entries use it.
• Discard Draft removes the unpublished draft and returns to the active schema if one exists.
• Revert restores unsaved edit-mode changes back to the last loaded schema draft.
• Cancel leaves edit mode and returns to the current saved schema view.

Import and export

• Import Schema can copy a schema structure from another tag or import a compatible schema payload when the current draft is empty.
• Export Schema downloads the current active or draft schema as a JSON file so it can be reused or backed up.
• Importing replaces the current empty draft with the imported field structure, so review it before saving or publishing.