Manage schemas

A schema defines the fields and validation rules used by capture forms and reports. Open it from Schemas to review its name, description, fields and permissions.

Schema definitions are versioned. Before changing a schema that already has metadata, review the impact on saved values and report filters. Follow any reconciliation work in Processes.

Review space, label and group restrictions when a schema moves to a new workflow or audience. A macro only offers schemas eligible for its page and user.

The visual Schema Builder supports text, numbers, booleans, enums, dates, email and URL formats, Confluence users, pages and spaces, arrays and nested objects. Use required fields and constraints for values that must be present or follow a specific shape.

Order and describe fields so the capture form reads like the work people already do. Static defaults and contextual defaults such as today or the current user reduce repeated typing without changing the underlying schema contract.

Definitions are versioned so a historical metadata can be interpreted with the schema that produced it. When a change affects existing documents or indexed values, review the impact preview and use reconciliation rather than assuming saved metadata will change by themselves.