S
Simpleasyty
Help Center — Introduction to Simple Metadata
GET STARTED
Simple Metadata demoIntroduction to Simple MetadataQuick start
CREATE & MANAGE SCHEMAS
Schemas, fields and templatesIndexed fields and filtersSchema permissions
CAPTURE DATA ON PAGES
Capture metadata on a pageCapture, validate and repair an entry
CREATE REPORTS
Build a Metadata ReportConfigure report filters and viewer controls
ADMINISTRATION & TROUBLESHOOTING
Entries, history and revisionsImport and exportSchema reconciliation and processesSecurity, storage and limitsTroubleshoot schemas, filters and reports

Introduction to Simple Metadata

Turn Confluence pages into structured, validated, reportable data.

GET STARTED

THE DATA LAYER

One schema connects capture, validation and reporting.

Use the same definition wherever a team needs consistent page data.

Define

Create a reusable schema for the fields and constraints that matter.

Capture

Collect one structured entry for a page and schema.

Report

Review matching entries across Confluence.

1

A data layer for Confluence pages

Simple Metadata lets administrators define schemas and lets authors capture structured values on individual Confluence pages. The same schema drives capture forms, validation, history and reports.

2

A compliance evidence layer

For compliance teams, a schema can represent a repeatable control or evidence record: control ID, scope, owner, status, evidence reference, approval and next review. Template the record once, then capture the same shape wherever the control is performed.

3

How it works

A schema defines fields, types, constraints, permissions and optional indexed fields. A capture macro stores one document for a page and schema. A report macro lists matching entries across the site.

  1. 1 Schemas are the source of truth
  2. 2 Entries are attached to pages
  3. 3 Indexed fields make reports filterable

The record behind the page

A schema is the source of truth for fields, types, constraints, permissions and indexed paths. An entry is one JSON document for one page and one schema; the capture form, validation state and reports all read that definition.

Live schemas and entries are stored in Forge SQL. Selectively indexed values support report filtering, while entry snapshots and schema revisions are retained separately for history.

Choose the right starting point

Use Simple Metadata when a page needs a governed, repeatable record rather than an informal two-column table. Start small: identify the owner, status, scope, evidence reference and next review date that readers need to compare.

  • Define the schema once
  • Place a capture macro where authors work
  • Publish a report for cross-page review

A practical evidence workflow

A control owner needs a consistent record without moving work into another system.

Before
Each page uses a different table or free-form notes, so review status is hard to compare.
With Simple Metadata
A shared schema captures the same fields on every page and a report brings the entries together.

Next step: Quick start