Storage in Forge — Simpleasyty

Help Center — Storage in Forge

GETTING STARTED

Introduction Quick start

CREATE A SCHEMA

Create a schema from a template Create a schema from scratch

SCHEMA TEMPLATES

Security Risk Register ISO 27001 Document Control SOC 2 Evidence Register Policy Management Third-Party Risk Data Classification Application Portfolio Controlled Document Architecture Decision Record Information Asset Register Business Continuity Register GDPR Processing Activity

IMPORT

Import a JSON or YAML schema package Import Page Properties

FIELD TYPES

Schema field types Text fields Number fields Yes / No fields Single choice fields Date / Time fields Email fields URL fields Confluence reference fields List fields Field group fields

MANAGE SCHEMAS

Manage schemas Indexed fields and filters Schema permissions

CAPTURE DATA ON PAGES

Capture metadata on a page Capture, validate and repair metadata

CREATE REPORTS

Build a Metadata Report Configure report filters and viewer controls

STORAGE & PRIVACY

Data residency Storage in Forge Retention and deletion

COMPLIANCE

Compliance workflows Metadata, history and revisions

ADMINISTRATION & TROUBLESHOOTING

Import and export Schema reconciliation and processes Security, storage and limits Troubleshoot schemas, filters and reports

Forge SQL

Live schema definitions, current metadata for each page and schema, and the selected index values used by report filters are stored in Forge SQL. Background jobs also use app storage. Forge provisions storage for the app installation on Atlassian infrastructure.

Forge KVS

Previous metadata values are saved as history snapshots in Forge KVS. Schema definition revisions are retained separately so earlier records can be interpreted with their definition.

Storage is managed by the app

Metadata has no Store as selector for individual records. Editors cannot choose page content, an attachment or Forge storage for metadata, as they can for a static Simple Tables table. Saved metadata remains associated with its Confluence page and schema.