S
Simpleasyty
Help Center — Metadata, history and revisions
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

COMPLIANCE

Metadata, history and revisions

Understand live metadata, metadata snapshots and schema versions.

Metadata

The Metadata view lets administrators inspect, filter, export and remove captured data. Metadata is associated with a page and schema.

History

Updating saved metadata archives the previous document. Metadata snapshots are retained in Forge KVS for 90 days. Schema definition revisions are retained so historical values remain interpretable.

Use Metadata for administration

The Metadata view lets administrators select a schema, inspect saved page data, apply indexed filters, check compliance, open history, export packages and remove metadata. Readable page, space and entity labels are enriched for review rather than exposing only raw identifiers.

Deleting metadata removes its current metadata and attempts to remove all retained historical versions and matching metadata macros from the page. If history cleanup fails, retained versions may remain until their 90-day expiry. Treat deletion as a record-management action, not a way to hide a value temporarily.

Understand history

Saving over metadata creates a snapshot of the previous document. Snapshots keep the schema version that applied at the time, while current and historical data can be compared during review. Metadata snapshots are retained for 90 days.