The standard Page Properties Report is an exercise in reductionism. It takes the complex, messy narrative of a wiki page—a tapestry of prose, images, and threaded comments—and flattens it into a single row. One page, one row. This is the "Sovereign Row."
Specify exactly which keys from your source tables should appear as columns, and in what order. This allows you to hide internal metadata while displaying key metrics.
Do not build your pages from scratch every time. Create a master template or standard page blueprint first. confluence page properties report multiple rows
The Page Properties Report macro is one of Confluence’s most powerful tools for building dynamic dashboards. It pulls metadata from multiple pages and aggregates it into a single, clean overview table. However, users frequently run into a common frustration: instead of a comprehensive table showing all their project statuses, tasks, or assets, the report only shows a single row or displays incomplete data.
However, a common question arises:
But when we need multiple rows where we see one, we are forced to admit defeat. We must acknowledge that the "Page" is too heavy a unit of measurement for granular data. We must migrate that data to a system where the "row" is the atomic unit, not the page.
This workflow effectively pulls from every source table, regardless of whether a page holds one row or fifty. The standard Page Properties Report is an exercise
This add-on provides a more flexible and customizable way to display multiple rows of data in a Confluence page properties report.
If you need to display multiple rows from one page, you can insert several on that same source page. This is the "Sovereign Row
But that’s still heavy. So Alex built a simpler trick: