S
Simpleasyty
Help Center — Introduction
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

GETTING STARTED

Simple Metadata documentation

Start with an overview of schemas, capture and reports.

Runs on Atlassian

Simpleasyty develops Simple Metadata on Atlassian Forge. The app has the Runs on Atlassian badge: Atlassian hosts its compute and storage and checks requirements for data residency and external connections. Captured metadata is not stored in a separate Simpleasyty database.

Why structured metadata matters

Details such as owner, status and next review date often vary from one Confluence page to another. A schema gives pages the same fields and rules, so teams can check values and compare them in reports across pages.

Where the data comes from

Authors enter values through the Simple Metadata macro on a page. You can also import existing Page Properties or bring in schemas from a JSON or YAML package. Page Properties import copies the values; it does not keep them in sync.

Where the data is stored

Metadata is linked to Confluence pages, but its values live in the app's Forge storage rather than in page content. Live schemas, metadata and report indexes use Forge SQL; history and schema revisions use Forge KVS. There is no storage selector for individual records.