ADD DATA
Page Properties
Turn structured information across many Confluence pages into one live table. It is ideal for project portfolios, decision logs, or request registers where every page carries the same important fields.
What happens when pages are read
The source reads the native Page Properties macros stored on published pages in one selected space. Choose one or more labels: a page matches when it has any selected label, and it appears only once even when it has several. Converting an existing Page Properties Report replaces the report with a live Simple Table macro; the properties on its source pages remain the source.
Build a live overview
The editor shows Search, Columns and Preview together. Follow these steps to turn matching pages into a table.
- 1
Choose Page Properties
Add a Simple Table macro, open Integrations, and select Page Properties.
- 2
Find the pages
Choose one space and one or more labels, then select Find pages. A page needs any of the selected labels and a Page Properties macro. Matching several labels does not duplicate its row. The scan shows progress and can process up to 5,000 matching pages.
- 3
Choose the fields
Select property keys in Columns and adjust their types if needed. Selected fields move to the top; the Preview shows up to ten rows.
- 4
Configure and publish
Choose Configure table and check the full result. The Settings preview footer shows the saved space and all selected labels, so you can confirm the source scope. Then save or publish the page. Use Refresh when you need changed values immediately.
Tip
Use the same property names on every page in the same register. It makes the table easier for readers to understand and keeps columns stable across pages.
Convert an existing Page Properties Report
On a published page, the conversion banner can offer native Page Properties Reports whose filters and settings can be kept in Simple Tables. Review the report before confirming its replacement.
- 1
Open the migration workspace
Choose Start migration. Tables and reports share one list; each report keeps its own space and labels. Select a report to inspect. For an initial report preview, choose Preview report in the centered introduction. Pending page edits must be published first using the steps below.
- 2
Load and compare the report
An animated loader shows progress while the matching pages are read. Once verified, compare Current data with the interactive Preview, including page title links and detected column formats. Search, sort, filter and page through the result without changing the source. If the report cannot be verified, retry before converting.
- 3
Convert one report or all eligible content
Use the Convert button naming the selected report. Select the Convert all checkbox beside it to include every eligible table and report. Each report retains its source space, labels and supported property columns. All selected replacements publish together in one new page version.
- 4
Explore the live result
The completion view shows the verified converted report, with tabs for multiple converted items. The discovery sidebar links to guides and a live Confluence demo in new tabs. View updated page opens the published result. The Simple Table macro continues reading the original source pages; open its settings to adjust formats, add property columns or change labels.
Good to know
A draft identical to the published page does not block conversion. If the page or saved draft changes after review, the preview is rebuilt and you must review and confirm again. Canceling review does not publish anything. Any selected report that cannot be read safely stays native.
Understand the migration preview
The same comparison is available for native tables and Page Properties Reports. Choosing a preview does not publish changes.
Current data
Read the original values in a read-only Confluence-style table, with links and supported native formatting. It has no Simple Tables search, sorting or detected display formats.
Preview
Try the Simple Tables result with search, filters, sorting and pagination. These interactions stay local. When you confirm conversion, the detected column settings are saved with the macro.
Column formats detected from your data
Categories
Repeated text values can become colored Enum categories. Existing native status colors and rich content are preserved.
Numbers, currencies and percentages
Numeric columns use suitable number or currency formatting and right alignment. Explicit percentages between 0 and 100 can appear as progress bars.
Dates and boolean values
Unambiguous YYYY-MM-DD dates can use Confluence-style date pills. Complete true/false or yes/no columns can use boolean indicators.
Detection is conservative: ambiguous dates and codes with leading zeros stay as text. Links and native rich content are kept. Review the result and adjust column types and formats in macro settings when needed; calculations and grouping are choices you configure yourself.
Continue when a page has unpublished changes
Unpublished title or content changes pause previews and conversion for every table and report on the page, even if only one item changed. Wait for Confluence to save changes in any open editor, then publish them before reviewing again.
- 1
Publish in the Confluence editor
Choose Open editor to publish. The editor opens in the same tab. Review all pending changes, including collaborators’ saved edits, then use Confluence’s Publish or Update button.
- 2
Review the updated content and convert
After publishing, check the page outside the editor. If the banner shows the initial suggestion, choose Start migration again. The review reloads current content and clears previous selections. Select the tables or reports again and confirm only after checking the updated preview. If pending edits still appear, use I've published, check again.
Two separate page versions
Publishing pending edits creates a page version; conversion creates another. Without a different draft, conversion publishes just one new page version.
If the result cannot be confirmed
If the save response is missing or the saved result cannot be verified, a separate verification screen explains the outcome and offers Reload page. Reload, check the converted content on the page, then choose Edit and check that the same content is there. Simple Tables does not automatically repeat publication.
Published pages. This banner workflow applies to published Confluence pages. Live Docs are excluded from conversion suggestions.
Suggestions become less frequent
If you see suggestions without opening a conversion preview, reminders gradually become less frequent. This schedule is shared by your account across all pages on this site.
- 1
First active day
Up to five appearances during the 24 hours after the first suggestion.
- 2
Next active day
Up to two appearances during the next active 24-hour period.
- 3
Third active day
One appearance, followed by a seven-day wait.
- 4
Two weekly reminders
One reminder after seven days, then another seven days later.
- 5
Monthly reminders
After the second weekly reminder, wait 30 days. Suggestions then appear at most once every 30 days.
You stay in control
Time away never skips stages: the next period starts only when another suggestion is shown. Opening a preview holds the current stage for one cycle without resetting its quota or shortening the wait. Not here can hide a page for you; restoring hidden pages does not reset the schedule. Previously saved timed pauses remain in effect until they expire. No banner or tab appears during waiting periods.
When a conversion is suggested
Only content still waiting to be converted
Existing Simple Table macros do not trigger the banner. If all eligible tables and reports have been converted, the suggestion disappears. A newly added native table or report can make it appear again.
Filters that can be preserved
The report must resolve to one space and one or more labels. Reports covering all spaces or several spaces, or using options such as a Page Properties ID or custom sorting, are left native when those settings cannot be preserved. Supported visible property columns keep their order.
Source properties that can be read
Use a vertical field/value table, or a horizontal table with a header row and one row of values. Keep property names unique, including after capitalization is ignored. Merged cells, unreadable source pages and ambiguous property tables can prevent conversion.
Example: a project portfolio without a separate list
The team gives each project page the label “project” and records the same Page Properties fields on every page.
- Project Atlas page
- Status: On track · Owner: Maya · Budget: $80,000
- Project Beacon page
- Status: At risk · Owner: Sam · Budget: $45,000
- Portfolio table
- One row per project page. Readers can sort by budget or filter to see only projects at risk.
Updates and limits
The table reads published Page Properties from matching pages. Refresh it after source changes, and review the selected columns when new fields are added.
Scan
The scan checks up to 5,000 search results in the selected space with any selected label. It shows progress and counts skipped pages; details are shown for up to 25 skipped pages. Existing tables saved with one label continue to work.
Column types
Dates and numbers are detected when the populated values consistently fit that type. Native Confluence statuses can become colored Enum columns; other mixed values are shown as text.
Refresh
A recent browser result can be reused for up to five minutes. Use Refresh to fetch changed values immediately.
New fields
New property keys are not added as columns automatically. Open macro settings, select Columns, and add the new field.