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

Compliance workflows

Use schemas, validation, history and reports to collect consistent evidence across Confluence pages.

Define a consistent record

A schema can describe a control or evidence record with fields such as owner, status, evidence link and next review date. Required fields, types and constraints give authors the same form on every eligible page. Space, label and group rules limit where a schema can be used.

Check metadata for each page

The capture form validates values against the schema when they are saved. If saved metadata no longer matches the current schema, its compliance state helps an editor find the affected fields. Fix applies safe best-effort changes; a person must review any remaining fields before treating the record as complete.

Review changes and report

Metadata snapshots and schema revisions help explain earlier values and definitions. Reports bring metadata for the same schema together so reviewers can compare them across pages. Index only the fields needed for filters, such as status, owner or review date, and reconcile older metadata when an index is added later.

Understand the evidence boundary

Metadata history is a time-limited snapshot history, not an immutable long-term audit log. Snapshots are retained for up to 90 days, and exported packages are not a backup that can restore metadata through package import. Set your own retention and approval process for formal compliance evidence.