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 — Create a schema from a template
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. Create a schema from a template

CREATE A SCHEMA

Create a schema from a template

v2.1.0+

Start with prepared fields, then adapt the schema to your work.

Before you begin

Check these requirements before following the steps below.

  • Access to the Simple Metadata app's Schemas tab.
  1. 1

    Open the schema wizard

    Open Simple Metadata, go to Schemas and select New schema. The first screen shows the template catalog.

  2. 2

    Choose a template

    Filter by category if useful. Select a template to preview its fields, then choose Continue. The template provides a starting definition; you can change its fields before saving.

  3. 3

    Review the schema

    In Schema setup, check the name, description, colour and fields. Change labels, required settings and constraints to fit your process. Index only fields you need to filter in reports.

  4. 4

    Set access and create

    Continue to Permissions, review where and by whom the schema can be used, then review and create it. You can then select it in a Simple Metadata capture macro on an eligible page.

Explore the included templates

Each template is a starting schema you can adapt. Explore its fields and the work it can support.

  • Security Risk RegisterGive every security risk a consistent record, so teams can compare exposure, assign treatment and revisit it on time.
  • ISO 27001 Document ControlApply a repeatable control record to policies and procedures so reviews, approvals and effective dates are easier to track.
  • SOC 2 Evidence RegisterKeep audit evidence tied to a control, a collection period and the people responsible for collecting and reviewing it.
  • Policy ManagementManage policies as a portfolio with clear ownership, approval status and scheduled review, rather than relying on page titles alone.
  • Third-Party RiskCreate one view of vendor exposure, security review and renewal so important supplier decisions are easier to follow.
  • Data ClassificationLabel Confluence content consistently and make ownership, sensitivity and retention visible to the teams handling it.
  • Application PortfolioBuild a searchable inventory of applications that connects business ownership, technology, cost and lifecycle.
  • Controlled DocumentUse one document record across teams to make approvals and review dates traceable even outside a specific framework.
  • Architecture Decision RecordKeep major technical decisions discoverable as systems and teams change, including decisions that replace earlier ones.
  • Information Asset RegisterInventory important information assets with enough context to assess ownership, sensitivity and review needs.
  • Business Continuity RegisterRecord recovery expectations for critical services and give continuity owners a consistent basis for planning and testing.
  • GDPR Processing ActivityStructure a processing-activity record so privacy teams can find ownership, legal basis, data categories and review information.