S
Simpleasyty
Help Center — Security, storage and limits
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

ADMINISTRATION & TROUBLESHOOTING

Security, storage and limits

Where Simple Metadata stores data and the limits to plan around.

Storage and personal data

Simple Metadata runs on Atlassian Forge. Live schemas, metadata and the report index use Forge SQL; metadata history and schema revisions use Forge KVS.

Customer-entered metadata can contain personal information, such as names, email addresses or contact details. This content is stored within Atlassian-hosted infrastructure, without being sent to a Simpleasyty-operated external data store.

Atlassian user references

User references are stored as accountIds. Display names and avatars are retrieved from Atlassian at runtime rather than persisted separately as profile data.

History and deletion

Previous metadata values are retained as metadata snapshots in Forge KVS for 90 days. Snapshots retain their schema version so historical values remain interpretable.

Deleting metadata removes its current metadata and attempts to remove all retained historical versions. If history cleanup fails, those versions may remain until their 90-day expiry. Deleting a schema schedules removal of its SQL data and retained metadata history; follow progress in Processes.

Usage limits

These limits determine how much data a request returns and which fields can narrow the results.

  • List and report requests return up to 500 metadata records. Use focused filters for larger datasets.
  • Fields must be indexed before they can be used for report filters. Reports use the schema’s field definitions and filter rules.

Troubleshooting

For a missing schema, check space, label and group eligibility. For missing filter results, check that the field is indexed and affected metadata has been saved or reconciled.