Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Use a Confluence database when you need structured entries with defined fields, reusable data, and multiple views. Use a table on a page when you simply need to present information as part of that page. Atlassian documents the database features, but does not publish a formal decision rule comparing databases with page tables; the distinction below follows from how each works.
How a Confluence database differs from a page table
A database is a structured Confluence content type. Its fields define the information each entry can hold and appear as columns; entries hold values and appear as rows. Databases live in the content tree and can be searched and linked. A page table, by contrast, is a presentation of information within the page where it appears.
The practical difference is whether the information needs to function as a reusable collection or mainly needs to be read in context. A database can support different arrangements of the same entries. A page table keeps its information directly alongside the page’s explanation.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsChoose based on how people will use the information
| Choose a Confluence database when… | Choose a table on a page when… |
|---|---|
| You have repeated entries that share a defined set of fields. | You need a straightforward presentation within one page. |
| Different readers or tasks call for different filters, sorting, layouts, or visible fields. | One shared arrangement is enough; readers do not need database views. |
| You want a structured collection that can be linked, searched, or embedded elsewhere. | The information makes sense as part of the surrounding page narrative. |
This is a practical comparison, not an official Atlassian feature matrix. The documentation describes database functionality and embedding, rather than prescribing when to use a page table.
#1 Best Overall
What database views add
A view lets you present the same database entries in a layout suited to a task or audience. Views can set a layout, filters, sorting, and which fields are hidden. For example, a team could keep one structured collection and use different saved views to show different slices of it.
Saved views can be shared by copying the browser URL or using Copy link. Temporary adjustments are personal to the current user and disappear after refreshing or navigating away, so use a saved view when other people need a stable arrangement.
Create and set up a database
- Start from Create in Confluence navigation, the plus control in the space content tree, or the editor’s insert menu. In the editor, you can also type
/database. - Choose a starting point: a template, CSV import, Jira connection, or blank database.
- Add fields to define the structure, then add entries and their values. In table layout, values can be entered or updated directly in the table; other layouts may show an entry dialog.
- Create and save views if people need different layouts, filters, sorting, or visible fields. Share a saved view using its link when others need that arrangement.
Atlassian says fields and entries are not limited, but notes that large databases may load more slowly and become complex. Plan the structure and views around the work people need to do rather than treating unlimited entries as a reason to put every kind of information in one database.
Put a database on a page
A database can be displayed on a page using Smart Links. This can make a database useful in both places: the structured collection remains a database, while a page gives readers a place to encounter it in context. Atlassian’s getting-started guide says database embedding and database macros are not enabled for Confluence templates.
Rank #3
Check permissions and availability first
Atlassian describes database permissions as managed at the space level. Confluence permissions can also include global, space, and content-level controls, but content restrictions are unavailable on the Free plan. Check the specific space and plan before relying on restricted access for database entries.
Atlassian states that databases are unavailable in the Atlassian Government environment. Confirm database availability in the intended tenant before choosing a workflow that depends on one.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
