S
Simpleasyty

STORAGE & PRIVACY

Atlassian Store: table data in Forge

Atlassian Store saves static table rows in Atlassian-hosted Forge storage. The macro keeps a reference instead of embedding the rows in the page or an attachment.

Choose where a table is saved

For tables made from pasted or uploaded data, Store as decides where Simple Tables keeps the rows. Your administrator chooses which options are available; changing the storage location does not change how the table works.

Store asWhere the source rows liveBest fit
Page ContentEmbedded in macro configuration, up to 100 KB.Small static datasets stored with the page.
AttachmentA file attached to the Confluence page.Table data that should travel with page or space exports.
Atlassian StoreAtlassian-hosted Forge storage, up to 5 MB per table.Static rows kept separate from page content and attachments.

Administrators: set the site policy

Site settings control which storage methods editors can choose and which one is selected by default for new tables.

  1. 1

    Open Apps → Simple Tables → Settings

    Only confirmed Confluence administrators can manage this tab.

  2. 2

    Enable Atlassian Store

    Choose which strategies editors may use. At least one must remain enabled. Drag an enabled strategy to the top to make it the default.

  3. 3

    Save changes

    The policy applies to future saves. Existing tables keep loading from their current storage; this does not bulk-migrate their data.

Editors: save a table in Atlassian Store

Use this option for pasted or uploaded table data when you want the rows stored in Atlassian Store instead of the page content or an attachment.

  1. 1

    Prepare a static table

    Paste or upload data in the Simple Table macro, then continue to table setup. Live URL, Join and native-table sources do not use this storage selector.

  2. 2

    Choose Store as → Atlassian Store

    The selector is in the editor footer. The option is available when the administrator enables it and the serialized data fits the 5 MB limit.

  3. 3

    Submit and publish

    The rows are saved to Forge and the macro references them. Optionally enable Data storage under Display → Context to show the storage location beside pagination.

Confidential and Incognito

Privacy and storage limits

Table content can contain personal information, such as names or email addresses, whichever storage method you choose. Atlassian Store stores it within Atlassian infrastructure, without sending it to a Simpleasyty-operated external data store.

Forge storage supports the host site’s data residency and Atlassian’s encryption policies. Analytics may report the storage mode, but not table values or attachment contents. External sources and explicit Rovo actions have separate data flows.

Access

Confluence page and space restrictions control the audience; writing requires page-edit permission. Enabled downloads, copying and screenshots remain possible.

Copies

a copied page or macro initially shares the stored data. Its first save on another page creates a separate payload.

Exports

Forge source rows are not included as page content or attachments in page exports. The rendered table remains visible; choose Attachment when table data needs to travel with exports.

Uninstalling

export first. Atlassian retains hosted app data for 28 days; reinstalling does not restore it automatically. Recovery requires the app developer and Atlassian.

Tip

Switching storage does not erase previous inline content, attachments, page history or exported copies.

Atlassian references

These Atlassian guides explain how Forge stores app data, where it is hosted and what happens after an app is uninstalled.