S
Simpleasyty
Help Center — Security, storage and limits
GET STARTED
Simple Metadata demoIntroduction to Simple MetadataQuick start
CREATE & MANAGE SCHEMAS
Schemas, fields and templatesIndexed fields and filtersSchema permissions
CAPTURE DATA ON PAGES
Capture metadata on a pageCapture, validate and repair an entry
CREATE REPORTS
Build a Metadata ReportConfigure report filters and viewer controls
ADMINISTRATION & TROUBLESHOOTING
Entries, history and revisionsImport and exportSchema reconciliation and processesSecurity, storage and limitsTroubleshoot schemas, filters and reports

Security, storage and limits

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

WORKFLOWS

1

Atlassian-hosted storage

Simple Metadata runs on Atlassian Forge. Live schemas and entries use Forge SQL; entry history and schema revisions use Forge KVS. Its core functionality does not send customer data outside Atlassian infrastructure.

2

Known limits

List and report requests are capped at 500 entries. Entry history snapshots have a 90-day retention period. Fields must be marked indexed before they can be used for report filters.

3

Troubleshooting

If a filter is unavailable, confirm that the field is indexed and entries have been saved or reconciled. If a schema is missing from a macro, review its space, label and group permissions.

Storage model

Simple Metadata runs on Atlassian Forge. Live schemas, entries and the selective report index use Forge SQL; history snapshots and schema revisions use Forge KVS. Core functionality keeps customer data within Atlassian infrastructure.

The schema remains the source of truth: reports derive their columns and filter policy from it rather than maintaining a separate data model for each report.

Operate within the limits

List and report requests are capped at 500 entries, and entry history snapshots expire after 90 days. Use focused indexed filters, concise reports and exports for larger review processes.

For missing schemas, check space, label and group eligibility. For missing filter results, check the field is indexed and that affected entries have been saved or reconciled.

Next step: Troubleshoot schemas, filters and reports