S
Simpleasyty
Help CenterCompareTrust CenterChangelogSupport
Marketplace
Help CenterCompareTrust CenterChangelogSupport Marketplace
Help Center
/Documentation/
GETTING STARTED
IntroductionQuick start
CREATE A SCHEMA
Create a schema from a templateCreate a schema from scratch
SCHEMA TEMPLATES
Security Risk RegisterISO 27001 Document ControlSOC 2 Evidence RegisterPolicy ManagementThird-Party RiskData ClassificationApplication PortfolioControlled DocumentArchitecture Decision RecordInformation Asset RegisterBusiness Continuity RegisterGDPR Processing Activity
IMPORT
Import a JSON or YAML schema packageImport Page Properties
FIELD TYPES
Schema field typesText fieldsNumber fieldsYes / No fieldsSingle choice fieldsDate / Time fieldsEmail fieldsURL fieldsConfluence reference fieldsList fieldsField group fields
MANAGE SCHEMAS
Manage schemasIndexed fields and filtersSchema permissions
CAPTURE DATA ON PAGES
Capture metadata on a pageCapture, validate and repair metadata
CREATE REPORTS
Build a Metadata ReportConfigure report filters and viewer controls
STORAGE & PRIVACY
Data residencyStorage in ForgeRetention and deletion
COMPLIANCE
Compliance workflowsMetadata, history and revisions
ADMINISTRATION & TROUBLESHOOTING
Import and exportSchema reconciliation and processesSecurity, storage and limitsTroubleshoot schemas, filters and reports
Help Center — Capture metadata on a page
GETTING STARTED
IntroductionQuick start
CREATE A SCHEMA
Create a schema from a templateCreate a schema from scratch
SCHEMA TEMPLATES
Security Risk RegisterISO 27001 Document ControlSOC 2 Evidence RegisterPolicy ManagementThird-Party RiskData ClassificationApplication PortfolioControlled DocumentArchitecture Decision RecordInformation Asset RegisterBusiness Continuity RegisterGDPR Processing Activity
IMPORT
Import a JSON or YAML schema packageImport Page Properties
FIELD TYPES
Schema field typesText fieldsNumber fieldsYes / No fieldsSingle choice fieldsDate / Time fieldsEmail fieldsURL fieldsConfluence reference fieldsList fieldsField group fields
MANAGE SCHEMAS
Manage schemasIndexed fields and filtersSchema permissions
CAPTURE DATA ON PAGES
Capture metadata on a pageCapture, validate and repair metadata
CREATE REPORTS
Build a Metadata ReportConfigure report filters and viewer controls
STORAGE & PRIVACY
Data residencyStorage in ForgeRetention and deletion
COMPLIANCE
Compliance workflowsMetadata, history and revisions
ADMINISTRATION & TROUBLESHOOTING
Import and exportSchema reconciliation and processesSecurity, storage and limitsTroubleshoot schemas, filters and reports
  1. Home/
  2. Help Center/
  3. Capture metadata on a page

CAPTURE DATA ON PAGES

Capture metadata on a page

v2.1.0+

Configure the Simple Metadata macro and collect structured values.

Configure the macro

Insert Simple Metadata, select one eligible schema and optionally enable the on-page history timeline. Add another macro if a page needs a separate schema.

Choose what readers see

Choose a normal, compact or card field layout. You can hide empty fields in page view, show the block only to page editors, or hide the block entirely while retaining its saved metadata for reports.

Validate and repair

The generated form validates data against the schema. Existing metadata displays compliance state; the repair action applies best-effort fixes and highlights fields that still need review.

Configure the page experience

Select one eligible schema for each capture macro. A page may use more than one macro when it needs separate records, but metadata for each page remains scoped to its page and selected schema.

Choose whether to show the schema heading, compliance state and history timeline. The history control lets readers inspect earlier saved versions; the compliance state signals whether the current document satisfies the schema.

Display and access options

Normal layout gives fields more space, compact reduces vertical space, and cards separate fields visually. Hide empty fields when a reader-facing page should focus on completed data; editors still see the fields needed to complete the metadata.

Editors-only limits the rendered block to people who can edit the page. Hide macro removes the block from page view entirely, while preserving its saved metadata for Metadata Reports and the management views.

Validation and repair

The form checks required values, types, formats and constraints before save. When an existing metadata is not compliant, the repair action applies safe best-effort changes and highlights any fields that still need human review.