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.
DATA STORAGE
Choose where a table is saved
| Store as | Where the source rows live | Best fit |
|---|---|---|
| Page Content | Embedded in macro configuration, up to 100 KB. | Small static datasets stored with the page. |
| Attachment | A file attached to the Confluence page. | Source files that should travel with page or space exports. |
| Atlassian Store | Atlassian-hosted Forge storage, up to 5 MB per table. | Static rows kept separate from page content and attachments. |
Administrators: set the site policy
Open Apps → Simple Tables → Settings
Only confirmed Confluence administrators can manage this tab.
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.
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
Prepare a static table
Paste or upload data in the Simple Table macro, then open Table features. Live URL, Join and native-table sources do not use this storage selector.
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.
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
Confidential selects and locks Atlassian Store. It is a handling label, not an access restriction. Confidential guide →
Incognito also locks Atlassian Store and withholds protected columns and dependent formulas from readers without page-edit permission. Existing tables must be saved again to apply this protection. Incognito guide →
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 source files need to travel with exports.
- Switching storage does not erase previous inline content, attachments, page history or exported copies.
- Uninstalling: export first. Atlassian retains hosted app data for 28 days; reinstalling does not restore it automatically. Recovery requires the app developer and Atlassian.