Confluence data workflow comparison
Confluence databases or Simple Tables?
Databases and page tables solve related but different problems. Databases organize records across saved views; Simple Tables turns page or file-based tabular data into an interactive published table.
Choose a Confluence database for records and views
Atlassian databases support structured fields and saved table, card, and board layouts. They are appropriate when entries are maintained as a shared record set and teams need multiple views.
Choose Simple Tables for table-centric reporting
Simple Tables is useful when the source is a native page table, CSV, JSON, XLS, or XLSX and the desired output remains a table with calculations, grouping, formatting, and export.
Ask where the source of truth lives
If users should maintain individual records and switch between layouts, start with a database. If a page needs to present and analyze an imported or native table, start with Simple Tables.
Sources used for this guide
Related Simple Tables documentation
Frequently asked questions
Is Simple Tables a Confluence database replacement?
No. It is a table product, while Confluence databases are designed around structured records and saved views.
Can a Confluence database import the same files as Simple Tables?
Capabilities change over time, so verify current Atlassian documentation. Simple Tables explicitly documents CSV, JSON, XLS, and XLSX sources.
Which is better for calculated table reports?
Simple Tables documents calculated columns, expression functions, grouping, and aggregations specifically for table outputs.