Schemas, fields and templates
Define the structure, validation and presentation of metadata.
SCHEMA & GOVERNANCE
Build a schema
Schemas are structured definitions edited through the visual Schema Builder. Definitions are versioned when fields change, so historical entries can be read against the definition that created them.
Field capabilities
Use text, numbers, booleans, enums, dates, email and URL formats, Confluence users, pages and spaces, arrays and nested objects. Fields can be required, ordered, described and constrained.
Templates and defaults
Start from Project Metadata, Meeting Notes, Vendor Record, or Poor man's workflow. Static defaults and contextual defaults such as today or the current user reduce repeated entry work. You can adapt a template into a control register, vendor review or certificate evidence record without changing the capture workflow.
Design fields for the people who enter data
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.
Changing a live definition
Definitions are versioned so a historical entry 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 entries will change by themselves.
Next step: Indexed fields and filters